Reduced size user interface

ABSTRACT

Techniques for a displaying user interfaces screens of a calendar application include displaying different screens based on an input modality. The calendar application may respond differently to inputs from a touch-sensitive screen, inputs from a rotatable input mechanism, inputs having higher intensities, inputs having lower intensities, and so forth.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.17/103,436, “REDUCED SIZE USER INTERFACE,” filed Nov. 24, 2020, which isa continuation of U.S. application Ser. No. 16/265,938, now U.S. Pat.No. 10,872,318, “REDUCED SIZE USER INTERFACE,” filed Feb. 1, 2019, whichis a continuation of U.S. application Ser. No. 14/752,776, “REDUCED SIZEUSER INTERFACE,” filed Jun. 26, 2015, which claims the benefit ofpriority of U.S. Provisional Application Ser. No. 62/129,848, “ReducedSize User Interface,” filed Mar. 8, 2015; U.S. Provisional ApplicationSer. No. 62/047,611, “Reduced Size User Interface,” filed Sep. 8, 2014;and U.S. Provisional Application Ser. No. 62/018,529, “Reduced Size UserInterface,” filed Jun. 27, 2014. The content of these applications ishereby incorporated by reference in its entirety for all purposes.

This application relates to the following applications: InternationalPatent Application Serial No. PCT/US2013/040061, entitled “Device,Method, and Graphical User Interface for Displaying User InterfaceObjects Corresponding to an Application,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/069483, entitled“Device, Method, and Graphical User Interface for Transitioning BetweenTouch Input to Display Output Relationships,” filed Nov. 11, 2013; andU.S. Patent Application No. 62/005,958, “Canned Answers in Messages,”filed May 30, 2014. The content of these applications is herebyincorporated by reference in its entirety for all purposes.

FIELD

The disclosed embodiments relate generally to user interfaces ofportable electronic devices, and specifically to user interfaces formanaging calendar information.

BACKGROUND

Consumers often store their calendars electronically. Those who own morethan one electronic device may wish to access their electronic calendarsfrom any device. Access to calendar information from portable electronicdevices is particularly desirable for mobile users. As portableelectronic devices become more portable—which will increase the desirefor electronic information access—suitable user interfaces for managingcalendar information will also become increasingly desirable.

SUMMARY

In some embodiments, techniques for presenting calendar informationcomprises, at an electronic device with a touch-sensitive display:displaying, on the touch-sensitive display, an icon representing acalendar application; detecting user input; in response to adetermination that the detected user input represents a touch on thedisplayed icon: launching the calendar application and transitioningfrom the display of the icon, through at least one intermediate userinterface screen, to displaying a landing screen of the calendarapplication; and in response to a determination that the detected userinput represents movement of the rotatable input mechanism: launchingthe calendar application and transitioning from the display of the icondirectly to displaying the landing screen of the calendar application.

In some embodiments, techniques for presenting calendar informationcomprises, at an electronic device with a touch-sensitive display:displaying, on the touch-sensitive display, an affordance representing acalendar application; detecting user input; in response to detecting theuser input: (a) in accordance with a determination that the detecteduser input is a touch on the displayed affordance: displaying a firsttext indicating at least two months in a year, then, replacing thedisplay of the first text with a display of a second text indicating atleast some days in one and only one month of the year, and then,replacing the display of the second text with a display of at least oneaffordance representing at least one calendar entry; (b) in accordancewith a determination that the detected user input is a movement of therotatable input mechanism: displaying at least one affordancerepresenting at least one calendar entry.

In some embodiments, techniques for presenting calendar informationcomprises, at an electronic device with a touch-sensitive display:displaying, on the touch-sensitive display, an affordance representing acalendar application; detecting user input; in response to detecting theuser input: (a) in accordance with a determination that the detecteduser input is a touch on the displayed affordance: displaying a firsttext indicating at least two months in a year, then, replacing thedisplay of the first text with a display of a second text indicating atleast some days in one and only one month of the year, and then,replacing the display of the second text with a display of at least oneaffordance representing at least one calendar entry; (b) in accordancewith a determination that the detected user input is a movement of therotatable input mechanism: displaying the first text indicating at leasttwo months in a year.

In some embodiments, techniques for presenting calendar informationcomprises, at an electronic device with a touch-sensitive display:displaying an affordance representing a calendar entry in a calendarapplication; detecting a touch on the display, the touch having acharacteristic intensity, the touch located at the displayed userinterface object representing the calendar entry; determining whetherthe characteristic intensity of the touch is below a thresholdintensity; in response to a determination that the characteristicintensity of the touch is below the threshold intensity, displaying atime and a location associated with the calendar entry; in response to adetermination that the characteristic intensity of the touch is notbelow the threshold intensity, displaying, on the touch-sensitivedisplay, a plurality of affordances representing functions of thecalendar application.

In some embodiments, techniques for presenting calendar informationcomprises, at an electronic device with a touch-sensitive display:displaying, on the touch-sensitive display, a plurality of calendarentries, the plurality of calendar entries including a first calendarentry and a second calendar entry, the first calendar entry displayedabove the second calendar entry; receiving user input representing useracceptance of the first calendar entry; and in response to receiving theuser input, displaying the first calendar entry below the secondcalendar entry.

In some embodiments, techniques for presenting calendar informationcomprises, at an electronic device with a touch-sensitive display:displaying, on the touch-sensitive display, a first user interfacescreen having a plurality of calendar entries; receiving first datarepresenting user acceptance of a first calendar entry of the pluralityof calendar entries; in response to receiving the first data, removingthe accepted first calendar entry from the first user interface screen;receiving second data representing a user input; and in response toreceiving the second data, replacing the display of the first userinterface screen with a display of a second user interface screen havinga plurality of accepted calendar entries.

In some embodiments, techniques for presenting calendar informationcomprises, at an electronic device with a touch-sensitive display:displaying a user interface screen on the touch-sensitive display,wherein the displayed user interface screen includes a plurality oftexts indicating a plurality of months in a year, wherein the texts ofthe plurality of texts are organized according to a layout having atleast two rows and at least two columns, wherein the plurality of textshave an initial visual characteristic; detecting a user selection of afirst text of the plurality of texts, the first text indicating a firstmonth of the plurality of months; and in response to detecting the userselection, changing the visual characteristic of the plurality of textsexcept the first text indicating the first month.

In some embodiments, techniques for presenting calendar informationcomprises, at an electronic device with a touch-sensitive display:displaying a row of numerals, the numerals indicating days in a month;detecting user input; and in response to detecting the user input,translating all but one of the displayed numerals from its respectiveposition in the row into a new position, wherein the displayed numerals,in their new positions, form a column of numerals.

In some embodiments, techniques for presenting calendar informationcomprises, at an electronic device with a touch-sensitive display: at anelectronic device with a touch-sensitive display: displaying on thetouch-sensitive display: text indicating hours in a day, at least oneregion representing a calendar entry scheduled during the indicatedhours, and text inside the at least one region indicating a name of thecalendar entry; detecting user input representing a zoom-in or zoom-outcommand; in accordance with a determination that the user inputrepresents a zoom-in command: enlarging the at least one region, anddisplaying additional text inside the at least one region indicatingdetails of the calendar entry.

In some embodiments, techniques for presenting calendar informationcomprises, at an electronic device with a touch-sensitive display:displaying, on the touch-sensitive display, an application affordancerepresenting a calendar application; detecting a user selection of theapplication affordance; in response to detecting the user selection ofthe application affordance: launching the calendar application;displaying a first event affordance representing a first calendar entry,and displaying a second event affordance representing a second calendarentry, wherein the second calendar entry is longer in duration than thefirst calendar entry, but the size of the first event affordance islarger than the size of the second event affordance.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having atouch-sensitive display in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 6A illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 6B illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 6C illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 6D illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 6E illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 6F illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 7A illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 7B illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 7C illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 7D illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 8A illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 8B illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 8C illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 8D illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 8E illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 9A illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 9B illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 9C illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 9D illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 9E illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 10A illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 10B illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 10C illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 10D illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 10E illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 11 illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 12A illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 12B illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 13 illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 14A illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 14B illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 15 illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 16 illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 17 illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 18 illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 19 illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 20A illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 20B illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 21 illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 22 illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 23 illustrates an exemplary calendar application user interfaceaccording to some embodiments.

FIG. 24 is a flow diagram illustrating a process for displaying userinterface screens for a calendar application.

FIG. 25 is a flow diagram illustrating a process for displaying userinterface screens for a calendar application.

FIG. 26 is a flow diagram illustrating a process for displaying userinterface screens for a calendar application.

FIG. 27 is a flow diagram illustrating a process for displaying userinterface screens for a calendar application.

FIG. 28 is a flow diagram illustrating a process for displaying userinterface screens for a calendar application.

FIG. 29 is a flow diagram illustrating a process for displaying userinterface screens for a calendar application.

FIG. 30 is a flow diagram illustrating a process for displaying userinterface screens for a calendar application.

FIG. 31 is a flow diagram illustrating a process for displaying userinterface screens for a calendar application.

FIG. 32 is a flow diagram illustrating a process for displaying userinterface screens for a calendar application.

FIG. 33 is a flow diagram illustrating a process for displaying userinterface screens for a calendar application.

FIG. 34 illustrates an exemplary computing system.

FIG. 35 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 36 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 37 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 38 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 39 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 40 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 41 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 42 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 43 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 44 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

User interfaces for efficient presentation and management of calendarinformation, particularly on portable electronic devices, are described.Below, FIGS. 1, 3, 5, and 34 provide a description of exemplary devicesfor managing calendar information on such devices. FIGS. 6A-6E, 7A-7D,8A-8E, 9A-9E, 10A-10E, 11, 12A-12B, 13-19, 20A-20B, and 21-23 illustrateexemplary user interfaces. The user interfaces are also used toillustrate the processes described below, including those in FIGS.24-33.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions, data on stores and otherpoints of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 2400-3300 (FIGS. 24-33).The computer-executable instructions can also be stored and/ortransported within any non-transitory computer-readable storage mediumfor use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer-readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer-readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 500 is not limited to the components and configurationof FIG. 5B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the term “open application” or “executing application”refers to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application may be any one of thefollowing types of applications:

an active application, which is currently displayed on a display screenof the device that the application is being used on;

a background application (or background processes), which is notcurrently displayed, but one or more processes for the application arebeing processed by one or more processors; and

a suspended or hibernated application, which is not running, but hasstate information that is stored in memory (volatile and non-volatile,respectively) and that can be used to resume execution of theapplication.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

1. Calendar User Interface Screens

Attention is now directed to user interface screens that support acalendar application that is operable on portable electronic devices. Inthe discussion that follow, device 500 (FIG. 5) is used repeatedly as anexample of a portable electronic device that supports calendarfunctionality, for sake of consistency and brevity. It is noted that thedescribed embodiments are not limited to device 500, and may beimplemented onto other portable electronic devices, for example devices100 and 300 (FIGS. 1 and 3).

Exemplary calendar user interface screens are now discussed withreference to FIGS. 6A-6E. FIG. 6A illustrates exemplary user interfacescreen 600 which may be referred to as the “month screen”. The monthscreen illustrates one or more days of a month. As shown, month 602(i.e., February) has twenty-eight days as indicated by the numbers “1”through “28.” Month screen 600 may visually emphasize the current day.In some embodiments, the current day is emphasized using an affordancesuch as affordance 604. In the illustrated example, affordance 604 has acircular shape and encircles the text (i.e., “16”) representing thecurrent day. Affordance 604 may, however, take on other shapes. In someembodiments, the current day is emphasized by altering the textrepresenting the current day. For example (not shown), the text may bebolded, brighten, flash, and/or become more opaque.

Month screen 600 is interactive. For example, month screen 600 may bescrollable to reveal days that are not already displayed, if any. Asanother example, month screen 600 may zoom. A user may initiate theseinteractions through different input modalities. In some embodiments,scrolling may be invoked via a touch gesture (e.g., swipe or flick). Insome embodiments, scrolling may be invoked via a physical inputmechanism (e.g., rotation of a rotatable mechanism). In someembodiments, zooming may be invoked via one or more of these mechanisms.

FIG. 6B illustrates exemplary calendar screen 610 which may be referredto as the “year screen”. Year screen 610 illustrates one or more monthsof a given year. As shown, the months of January to June of year 612(i.e., 2018) are at least partially displayed in year screen 610. Insome embodiments, the current day is emphasized using an affordance suchas affordance 614. In the illustrated example, affordance 614 has acircular shape and encircles the text (i.e., “2”) representing thecurrent day. Affordance 614 may, however, take on other shapes. In someembodiments, the current day is emphasized by altering the textrepresenting the current day. For example (not shown), the text may bebolded, brighten, flash, and/or become more opaque. Year screen 610 maybe interactive in that it may be, for example, scrollable and zoom-able.

FIG. 6C illustrates another exemplary year screen 620. In contrast toyear screen 610 (FIG. 6B), year screen 620 (FIG. 6C) has a center bias,meaning that the current day is displayed, by default, on or near thevertical center of touchscreen 504. Restated, when device 600 displaysyear screen 620, the current day is initially displayed in thecenter-most row of calendar days being displayed. As shown, the currentday (i.e., May 2) is marked by affordance 622. Year screen 620 may beinteractive in that it may be, for example, scrollable and zoom-able.

FIG. 6D illustrates exemplary calendar screen 630 which may be referredto as the “day screen”. Day screen 630 illustrates calendar entriesrepresenting events that have been scheduled for a given day. Day screen630 may have hour markers 632 indicating one or more hours in the day.Day screen 630 may have affordance 634 indicating the current time ofday. As shown, affordance 634 has a horizontal line residing atapproximately a quarter of the distance between the eight and nineo'clock hour markers. Affordance 634 thereby indicates current time asapproximately quarter-past eight o'clock.

Day screen 630 may indicate calendar entries of the day using regions636 and 638. Calendar entries may be stored on electronic device 500, acompanion device (e.g., a cellular phone), at a network-accessiblelocation (e.g., in the “cloud”), or in some combination thereof. Theseregions are contiguous regions that are visually distinguishable fromthe background of day screen 630. In some examples, these regions maytake on a geometric shape. As shown, region 636 and 638 are rectangularboxes. The edges of region 636 and 638 may indicate the start and endtimes of corresponding calendar entries. For example, region 636represents an event scheduled from nine o'clock to half-past ninebecause its top edge is aligned with the hour marker indicating 9o'clock. As another example, region 638 represents an event scheduledfrom ten o'clock to half-past eleven. Due to the correspondence betweenthe edges of regions 636 and 638 with the start/end times of theircorresponding calendar entries, the vertical heights of the regions areproportional to the durations of the respective calendar entries. Thispresentation of calendar entries imparts a grid-like appearance to dayscreen 230. Accordingly, day screen 630 may be referred to as the “grid”version of the day screen.

Day screen 630 also may have all-day entry indicator 639 indicating acalendared event that spans the day. In some examples, all-day entryindicator 639 is displayed above all other partial-day calendar entriesto promote its visibility. Note that, to reduce its on-screen footprint,the vertical height of all-day entry indicator 639 may be shortercompared to regions 636 and 638, even though its (all-day) duration islonger than that of the events represented by regions 636 and 638.

FIG. 6E illustrates another exemplary day screen 640. In contrast to dayscreen 630, day screen 640 displays calendar entries in a list-likelayout. Day screen 640 may have region 642 indicating an all-day eventthat is scheduled for the day. Day screen 640 also may have regions 644and 646 indicating additional (partial-day) calendar entries scheduledfor the day. As shown, regions 642, 644, and 646 may abut one another insuccession. The presentation of calendar entries sequentially abuttingone another imparts a list-like appearance to day screen 640.Accordingly, day screen 240 may be referred to as the “list” version ofthe day screen.

Day screen 640 also may have affordances 648 and 649 indicating thesource of the represented calendar entries. (As discussed above, it ispossible for device 500 to have access to more than one calendar.)Calendar indicator 648 may indicate that “John's Birthday” resides in afirst calendar such as a personal calendar, while calendar indicator 649may indicate that “Meeting B” resides in a second calendar such as workcalendar.

FIG. 6F illustrates exemplary calendar entry details screen 650, whichmay indicate detailed information regarding a calendar entry. As shown,entry details screen 650 may include event name 652, event location 654,event date 656, event time 658, and/or event organizer 660. Entrydetails screen 650 may also include participant information, such asindications of participants indicating planned attendance 662,indications of participants indicating planned absence (not shown),and/or indication of participants who have not replied to eventorganizer 664. Calendar entry details screen 650 may include reminderoption 666, which permits a user to elect a reminder alert. In someexamples, the reminder alert alerts a user a fixed amount of time priorto an event. In other examples, the reminder alert alerts an amount oftime prior to an event corresponding to an amount of time required forthe user to reach the event. Calendar entry details screen 650 alsoinclude option 668 for adjusting the user's presence information,meaning that option 668 controls whether the calendar application markthe meeting time as busy (or free) on the user's calendar. Calendarentry details screen 650 may include calendar indicator 670 identifyingon which the subject calendar entry is stored, such as a work calendar.

2. Transitions between Calendar Screens

Attention is now directed to ways in which embodiments of the calendarapplication may, in response to user interaction, transition between thedisplays of the calendar screens described with respect to FIGS. 6A-6F.These transitions are discussed with reference to FIGS. 7A-7D.

FIG. 7A illustrates an exemplary screen flow 700. As shown, device 500may display user interface screen 701 having icons 702-706. Icons702-706 may correspond to applications executable on device 500, meaningdevice 500 may launch a corresponding applications in response to auser's selection of an icon. In the illustrated example, icon 702corresponds to a calendar application. Thus, in response to a selectionof icon 702, device 500 may launch the calendar application. In someembodiments, user selection of icon 702 may occur via a touch gesture(e.g., tap, touch and hold, swipe, flick). In some embodiments, theselection may occur via a physical input mechanism (e.g., rotation of arotatable mechanism).

As shown in FIG. 7A, a user may contact (e.g., touch) displayed icon702. In response, device 500 may launch the corresponding calendarapplication. Upon launching, the calendar application causes device 500to display the follow user interface screens in sequence: day screen708, to month screen 709, and to year screen 710. The display of screens708-710 is sequential and automatic in that device 500 displays thescreens in order, one after the other, without requiring further userinput beyond touch contact 707. Screens 708 and 709 may each bedisplayed for a predetermined amount of time before the next screen isdisplayed.

In flow 700, year screen 710 is the landing screen for the calendarapplication, meaning that, if user invoked the calendar applicationusing touch contact 707, the calendar application would launch andsettle into the display of year screen 710. Flow 700 presents calendarinformation to a user in a decreasing level of granularity, as the useris initially presented calendar information for the day, followed by themonth, and followed by the year.

FIG. 7B illustrates another exemplary screen flow 720. As shown, device500 may display user interface screen 701 having icons 702-706. A usermay touch displayed icon 702. In response to a user selection of icon702, device 500 may launch the calendar application. Upon launching, thecalendar application may cause device 500 to display the follow screensin sequence: year screen 710, to month screen 709, and to day screen708. In flow 720, day screen 708 is the landing screen for the calendarapplication. In this way, flow 720 presents calendar information to auser in an increasing level of granularity.

FIG. 7C illustrates another exemplary screen flow 730. As shown, device500 may display user interface screen 701 having icons 702-706. Thecenter-most displayed icon, icon 702, may correspond to the calendarapplication. A user may move rotatable input mechanism 508 of device 500while icon 702 is the center-most displayed icon or perform a gesture(e.g., a tap, touch and hold, or flick) on the icon. In response, device500 may launch the calendar application corresponding to icon 702. Uponlaunching, the calendar application may cause device 500 to display dayscreen 708. Thus, day screen 708 is the landing screen in flow 730.While day screen 708 is displayed, the user may move rotatable inputmechanism 508 again. In response to further movement 737 of therotatable input mechanism, device 500 may replace the display of dayscreen 708 with month screen 709. While month screen 709 is displayed,the user may move rotatable input mechanism 508 again. In response tofurther movement 747 of the rotatable input mechanism, device 500 mayreplace the display of month screen 709 with year screen 310. As shown,movements 727, 737, and 747 are in the same direction of rotation. Inthis way, flow 720 presents calendar information to the user in adecreasing level of granularity while emphasizing the lower-level dayscreen initially (as the landing screen).

FIG. 7D illustrates another exemplary screen flow 740. As shown, device500 may display user interface screen 301 having icons 702-706. Thecenter-most displayed icon, icon 702, may correspond to the calendarapplication. A user may move rotatable input mechanism 508 of device 500while icon 702 is the center-most displayed icon or perform a gesture(e.g., a tap, touch and hold, or flick) on the icon. In response, device500 may launch the calendar application corresponding to icon 702. Uponlaunching, the calendar application causes device 500 to display yearscreen 710. Thus, year screen 710 is the landing screen in flow 740.While year screen 710 is displayed, the user may move rotatable inputmechanism 508 again. In response to further movement 737 of therotatable input mechanism, device 500 may replace the display of yearscreen 710 with month screen 709. While month screen 709 is displayed,the user may move rotatable input mechanism 508 again. In response tofurther movement 747 of rotatable input mechanism 508, device 500replaces the display of month screen 709 with day screen 708. As shown,movements 727, 737, and 747 are in the same rotation direction. In thisway, flow 740 presents calendar information to the user in an increasinglevel of granularity while emphasizing the higher-level year screeninitially (as the landing screen).

Attention is now directed to the defaulting behaviors of day screen 708,month screen 709, and year screen 710. In some embodiments, the displayof day screen 708 in the above-described flows (FIGS. 7A-7D) involvesdisplaying calendar entries for the current day, by default. That is,when day screen 708 is initially presented in these flows, calendarentries for the current day (if any) are displayed. In some embodiments,the displays of month screen 709 in the above-described flows involvedisplaying the days of the current month, by default. In someembodiments, the displays of year screen 710 (FIGS. 7A-7D) in theabove-described flows involve displaying the months of the current year,by default.

In some embodiments, the displays of day view 708 (FIGS. 7A-7D) in theabove-described flows involve displaying calendar entries for the mostrecently viewed day, by default. In some embodiments, the display ofmonth view 709 (FIGS. 7A-7D) in the above-described flows involvedisplaying days of the most recently viewed month, by default. In someembodiments, the display of year view 710 (FIGS. 7A-7D) in theabove-described flows involve displaying the months (and/or days) of themost recently viewed year, by default.

In some embodiments, device 500 supports both flows 700 and 740 suchthat it responds differently to input in the form of a selection (e.g.,707) of icon 702 versus input in the form of a rotational movement(e.g., 717), when screen 701 is displayed. Other combinations arepossible. In some embodiments, device 500 supports flows 700 and 730when screen 701 is displayed. In some embodiments, device supports flows720 and 740 when screen 701 is displayed. In some embodiments, device500 supports flows 720 and 730 when screen 701 is displayed. Othercombinations are permutations in different embodiments. In someembodiments, device 500 permits user-designation of preferred flow(s).

Among other things, the above-described user interface flowsbeneficially improve the efficiency of man-machine interface between auser and device 500. For example, in the described embodiments, device500 may present a user with multiple ways of winnowing and accessingspecific calendar entries out of a greater set of calendar information.Consider flow 720 (FIG. 7B), in which device 500 presents a user with avisual transition from year, to month, to day: This flow may help theuser focus onto the information that is ultimately presented (e.g.,information for today), yet it does not require the user to manuallynavigate (e.g., find and invoke navigational icons) from screen toscreen. This transition may be particularly helpful when a user does notyet know what day the calendar application is presently focused on(e.g., what day's calendar entries will the application display). At thesame time, device 500 may allow a user—who is already aware of the daythat is being focused on—to access the calendar information directly bya single input. Consider flow 730 (FIG. 7C), in which device 500 allowsa user to invoke the day screen directly. The availability of theseflows in a device such as device 500 permits a user to invoke the mostefficient interfaces for particular usage scenarios, thereby improvingthe quality and efficiency of the resulting man-machine interactions.

In addition, the availability of a rotatable input mechanism on device500 further improves the speed of these man-machine interactions. Forexample, after seeing device 500 transition between different calendarscreens (e.g., year, month, day) in flow 720 (FIG. 7B), a user mayrotate the input mechanism to quickly “flip” back to the desired screenthat he may have identified as being useful during the transition. Inthis way, device 500 may reduce (and in some instances eliminate)intermediate touch gestures involving navigational icons to retrieve thedesired user interface screen. Importantly, this combination of theavailable software user interface and hardware input mechanism permitefficient navigation between calendar screens and entries.

Attention is now directed to additional exemplary user interactions withthe calendar application executing on device 500. These aspects aredescribed with reference to FIGS. 8A-8E. FIG. 8A illustrates exemplaryday screen 800. Day screen 800 may be day screen 708 (FIG. 7A) in someembodiments. Day screen 800 includes text 802 indicating the day forwhich calendar entries are being displayed. As shown, day screen 800indicates calendar entries scheduled for the current day. Day screen 800also includes text 804 representing hours in the displayed day. Regions806 and 808 represent calendar entries scheduled for the current day.Day screen 800 also includes indicator 810 indicating an all-daycalendar entry scheduled for the current day. Note that the verticallength of all-day entry indicator 810 is shorter than that of regions806 and 808, even though an all-day event has a longer duration than theevents represented by regions 808 and 810. In this way, the calendarapplication is able to reduce the usage of on-screen space necessary fordisplaying all-day calendar entries. Day screen 800 also includesaffordance 812 indicating the current time. As shown, affordance 812 isa horizontal line, though it may take on another shape.

All-day calendar entry indicator 810 is responsive to user interaction.In some embodiments, having seen indicator 810, the user may select theindicator to reveal more information about the all-day event. In someembodiments, the selection is made with touch gesture such as a tap or aswipe (e.g., downward swipe 842) involving indicator 810. In response tothe user selection, the calendar application may enlarge all-day eventindicator 810 to reveal that today is “John's Birthday,” as indicated bytext 844.

As used here, a swipe need not be perfectly aligned with one directionin order for the swipe to be considered as a swipe in that direction.That is, a downward swipe need not be perfectly straight nor vertical inthe down direction. Instead, a swipe that is substantially in onedirection may be considered to be a swipe in that direction. In someexamples, a swipe that is within less than 45 degrees from an axis ismay be considered to be substantially along that axis. In some examples,particularly those in which a screen is scrollable only along one axis,a swipe that has any detectable motion along that axis may be considereda swipe substantially along that axis.

FIG. 8B illustrates additional exemplary user interactions with dayscreen 800. Day screen 800 includes region 808 representing a calendarentry for the displayed day. As shown, a user contacts (e.g., asindicated by tap 846) the touch-sensitive display of device 500 at thedisplay position of region 808. In response, device 500 may displaycalendar entry details screen 820. Calendar entry details screen 820 maybe calendar entry details screen 650 (FIG. 6F) in some embodiments.

FIG. 8C illustrates exemplary day screen 830 that is used to providedaily calendar information in some embodiments. Day screen 830 is dayscreen 708 (FIG. 7A) in some embodiments. Day screen 830 includes text832 indicating the day for which calendar entries are being displayed.Day screen 830 also includes text 834 representing hours in thedisplayed day, in this case, the current day. Regions 836 and 838represent calendar entries scheduled for the current day. Note that therepresented calendar entries are partially concurrent in that thescheduled meeting times overlap. To accommodate for the display ofconcurrent calendar entries, regions 836 and 838 are reduced in theirwidths so that the events can be represented on day screen 830. A usermay select (e.g., touch) one of the displayed regions 836 and 838 todisplay additional details regarding the represented calendar entries.The additional details are displayed via calendar entry details screen650 (FIG. 6F) in some embodiments.

FIG. 8D illustrates exemplary day screen 840 that is used to providedaily calendar information in some embodiments. Day screen 840 is dayscreen 308 (FIG. 3A) in some embodiments. Day screen 840 includes text842 indicating the day for which calendar entries are being displayed.Day screen 840 also includes text 844 representing hours in thedisplayed day, in this case, the current day. Regions 846, 847, and 848represent calendar entries scheduled for the current day. Note that theregions are displayed in an overlapping manner because they representcalendar entries that are (at least partially) concurrent. In this way,concurrent events are represented on-screen simultaneously. The displayof overlapping calendar entries in this manner may be referred to as“stacking” the display of calendar entries.

A user may select (e.g., touch) the displayed regions 846-848 to displayadditional event details for the represented calendar entries. In someembodiments, a selection of any one of the regions 846-848 causescalendar entries screen 850 to be displayed. Calendar entries screen 850has non-overlapping regions 852, 854, and 856 corresponding to regions846, 847, and 848, respectively. Regions 852, 854, 856 are presented ina non-overlapping manner on screen 850 to facilitate user selection. Auser may select any one of regions 852, 854, 856 to access detailedinformation for the represented calendar entry. The additional detailsmay be displayed via calendar entry details screen 650 (FIG. 6F).

In some embodiments (not illustrated), it is possible for a user tobypass calendar entries screen 850 by precisely selecting one of regions846-848 in day screen 840. For example, if device 500 detects userselection at a position that falls within a single displayed region(e.g., 847) and not another overlapping region (e.g., 846 or 848),device 500 displays details for the calendar entry represented by thesingle region (e.g., 847). The additional details may be displayed viacalendar entry details screen 650 (FIG. 6F).

FIG. 8E illustrates exemplary day screen 860 that is used to providedaily calendar information in some embodiments. Day screen 860 is dayscreen 708 (FIG. 7A) in some embodiments. Day screen 860 includes text862 indicating the day for which calendar entries are being displayed.Day screen 860 also includes text 864 representing hours in thedisplayed in day, in this case, the current day. Region 866 representsmultiple calendar entries scheduled for the current day between thehours of 9:30 am to noon. Region 866 includes text 868 indicating itsrepresentation of multiple calendar entries. Day screen 860 stands incontrast to day screen 830 (FIG. 8C) in that concurrent calendar entriesare not displayed side-by-side. Day screen 860 stands in contrast to dayscreen 840 (FIG. 8D) in that concurrent calendar entries are notdisplayed in a partially overlapping manner. Rather, day screen 860merges multiple calendar entries into the display of region 866. In someembodiments, the placement of the top of region 866 within screen 860corresponds to the start time of the earliest represented calendar entry(as defined by hour markers 864). In some embodiments, the bottom ofregion 866 corresponds to the end time of the latest representedcalendar entry. The display of merged calendar representations in thismanner may be referred to as “coalescing” the display of calendarentries.

A user may select (e.g., touch) region 866 to display calendar entriesscreen 870. Calendar entries screen 870 has regions 872, 874, and 876representing the multiple (in this case, three) calendar entries thathad been coalesced into and were represented by region 866. From screen870, a user may select any one of regions 872, 874, and 876 to accessdetailed information for the represented calendar entry. The additionaldetails may be displayed via calendar entry details screen 650 (FIG.6F).

3. Contextual Features

Attention is now directed to techniques for accessing contextual userinterfaces in embodiments of the calendar application. Device 500 mayhave a small form factor. Due to its size, device 500 may not lenditself to displaying large numbers of graphical user interface elements,as the inclusion of many elements could reduce the display areaavailable for calendar content.

In some embodiments, the calendar application of device 500 may invokedifferent features based on the touch intensity of user input. Thisaspect is described with reference to FIGS. 9A-9E. As shown in FIG. 9A,device 500 may display day screen 500 which may be day screen 800 (FIG.8) in some embodiments. A user may select (e.g., touch) region 908,which represents a calendar entry. Device 500 may determine ameasurement of the intensity of the selection (e.g., touch) and providedifferent responses based on the intensity. For example, if theintensity is below a threshold, the calendar application may displaycalendar entry details screen 910. Calendar entry details screen 910 maybe calendar entry details screen 650 (FIG. 6F) in some embodiments. Ifthe intensity is above the threshold, device 500 may display optionsscreen 920 instead of event details screen 910, even though the contactoccurred at a position of affordance 908 corresponding to a calendarentry.

Options screen 920 may include affordances for invoking various options(or features) of the calendar application. For example, options screen920 may include affordance 922 for displaying a day screen for thecurrent day. Options screen 920 may include affordance 924 displaying a“calendar inbox” screen. (Exemplary calendar inbox screens are describedbelow with reference to FIGS. 9C-9D.) Options screen 920 may includeaffordance 926 for displaying configuration settings related to dayscreen 900 and/or the calendar application. (Exemplary configurationscreens are described below with reference to FIG. 9E.) Options screen920 may include affordance 928 for toggling between a display of thelist and grid versions of the day screen.

Attention is now directed to calendar inbox screens that may be invokedusing affordance 924 on options screen 920 (FIG. 9A). FIGS. 9B and 9Cillustrate exemplary calendar inbox screens. FIG. 9B illustratesexemplary calendar inbox screen 930 having regions 932, 934, and 936corresponding to incoming calendar entry invitations. Calendar inboxscreen 930 may prioritize the display of new (e.g., unread or recent)invitations. In some embodiments, unread invitations are displayed nearthe top of calendar inbox screen 930 while invitations that have beenread are displayed, if displayed at all, towards the bottom of calendarinbox screen 930. In some embodiments, invitations are sorted by timereceived, meaning that more recent received invitations are displayedcloser to the top of calendar inbox screen 930. In this way, incominginvitations may still be displayed to the user even when a large numberof invitations are being managed through the calendar inbox. Calendarinbox screen 930 may be scrollable to reveal additional calendar entryinvitations.

FIG. 9C illustrate exemplary calendar inbox screens 950 and 952.Calendar inbox screen 950 may display new calendar entries received bydevice 500. As shown, regions 954 and 956 represent new calendar entries(e.g., invitations). For example, region 954 may represent the mostrecently received entry while region 956 may represent an entry that hasbeen received for a while but remains unread. Device 500 may receiveuser input representing swipe 958 while calendar inbox screen 950 isdisplayed. In response to the swipe input, device 500 may displaycalendar inbox screen 952. Calendar inbox screen 952 may display olderinvitations. For example, region 960 may represent an invitation thatthe user has answered.

Calendar inbox screens 950 and 952 may each include affordances 962 and964 indicating the position of each screen among a plurality of screens.Affordances 962 and 964 may enlarge, darken, or otherwise change invisual appearance when the corresponding calendar inbox screen isdisplayed. An exemplary implementation of affordances 962 and 964 ispaging dots.

Attention is now directed to configuration settings screens that may beinvoked using affordance 926 on options screen 920 (FIG. 9A). FIG. 9Dillustrates exemplary settings screen 970 for configuring calendarapplication settings. Configuration screen 970 may include affordancesfor configuring the calendar application. For example, configurationscreen 970 may include affordance 972 for selecting one or morecalendars to display in the calendar application. As another example,configuration screen 970 may include affordance 974 for specifyingwhether the calendar application displays calendar entries previouslydeclined by the user.

In some embodiments, device 500 may display calendar selection screen980 in response to a touch on affordance 972. Calendar selection screen980 may include a legend identifying visual representations used torepresent different calendars, such as the use of circle 982 torepresent calendar 984. Circle 982 may be affordance 670 (FIG. 6F) insome embodiments. Settings screen 980 may also include switches forcontrolling whether the events of certain calendars are to be shown inthe calendar application. For example, switch 986 may be used toindicate that the calendar application should display events of calendar984 (e.g., personal) while switch 988 may be used to indicate that thecalendar application should omit events of calendar 990 (e.g., work).

Attention is now directed to the toggling of different on-screenpresentations of calendar entries that may be invoked by affordance 928on options screen 920 (FIG. 9A). In some embodiments, a user may selectaffordance 928 to toggle between displaying calendar entries in a listformat (e.g., day screen 640 in FIG. 6E) or in a grid format (e.g., dayscreen 630 in FIG. 6D). As shown in FIG. 9E, while the day screen 990 isdisplayed in list format, a user may invoke options screen 992 andselect affordance 994 to redisplay day screen 996 in grid format.Options screen 992 may be options screen 920 in some embodiments. It isalso possible to return to the display of day screen 990 in list formatin the same manner.

The calendar application may display options screens other than optionsscreen 920 (FIG. 9A) in response to a touch contact that exceeds thethreshold intensity. In some embodiments, the displayed options may varydepending on which user interface screen of the calendar application isdisplayed at the time of the high-intensity touch contact. That is,option screens may be context-sensitive. Examples of additional optionsscreens that may be invoked in this way are described with reference toFIGS. 10A-10

FIG. 10A illustrates exemplary options screen 1000. In some examples,device 500 displays options screen 1000 if it receives a touch contactexceeding a threshold while it is displaying a day screen, such as dayscreen 1030 (FIG. 10D) and/or day screen 1040 (FIG. 10E). Options screen1000 may include affordance 1002 for causing device 500 to display theday screen for the current day. Option screen 1000 also may includeaffordance 1004 for causing device 500 to display calendar inbox 940(FIG. 9C). Options screen 1000 also may include affordance 1006 forcausing device to return to the day screen. Options screen 1000 also mayinclude affordance 1008 for causing device 500 to launch a calendarapplication on another computing device, such as a cellular phone, thatis within communications range of device 500. In some embodiments, whenaffordance 1008 is selected, device 500 may instruct the companiondevice to display the day screen for the same day that was most recentlydisplayed on device 500.

FIG. 6B illustrates exemplary options screen 1010. In some examples,device 500 displays options screen 1010 if it receives a touch contactexceeding a threshold value while it is displaying month screen 600(FIG. 6A) or year screen 610 (FIG. 6B). Options screen 1010 may includeaffordance 1012 for causing device 500 to display the day screen for thecurrent day. Options screen 1010 also may include affordance 1014 forcausing device 500 to display calendar inbox 930, 950, or 952 (FIGS. 9Band 9C). Options screen 1010 also may include affordance 1016 forcausing device to display a settings screen such as settings screen 970(FIG. 9D).

FIG. 10C illustrates exemplary options screen 1020. In some examples,device 500 displays options screen 1020 if it receives a touch contactexceeding a threshold value while it is displaying calendar entrydetails screen 650 (FIG. 6F). Options screen 1020 may include affordance1022 for causing device 500 to accept an invitation to the event that isdisplayed on the calendar entry details screen. Options screen 1020 alsomay include affordance 1024 to indicate possible attendance. Optionsscreen 1020 also may include affordance 1026 to decline attendance.Options screen 1020 also may include affordance 1028 for initiating anemail to the events' participants.

FIG. 10D illustrates exemplary options screen 1030. In some examples,device 500 displays options screen 1030 if it receives a touch contactexceeding a threshold value while it is displaying calendar selectionscreen 1080 (FIG. 10E). Options screen 1040 may include affordance 1042for causing device 500 to display the day view for the current day.Options screen 1040 also may include affordance 1046 for displaying asettings screen such as settings screen 970 (FIG. 9E).

FIG. 10E illustrates exemplary options screen 1040. In some examples,device 500 displays options screen 1040 if it receives a touch contactexceeding a threshold value while it is displaying calendar inbox 930,950, or 952 (FIGS. 9B and 9C). Options screen 1040 may includeaffordance 1042 for causing device 500 to display a day screen for thecurrent day. Options screen 1040 may include affordance 1044 forreturning to the calendar inbox screen. Options screen 1040 also mayinclude affordance 1046 for displaying settings screen 970 (FIG. 9E).Note that, although the affordances for invoking various display screensas discussed with respect to FIGS. 10A-10E are illustrated as beingcircular, they can take on other shapes. The affordances may berectangular, instead, for example.

4. Responding to Calendar Entries

Attention is now directed to how the calendar application permits a userto respond (e.g., accept or decline) to an incoming calendar entry(e.g., an invitation). With reference to FIG. 11, device 500 may displaycalendar inbox screen 1100, which may be screen 930 (FIG. 9B) in someembodiments. Calendar inbox screen 1100 may include region 1102representing a calendar invitation to “Meeting B.” If a user selects(e.g., touches) region 1102, the calendar application may cause device500 to display event details screen 1110. Screen 1110 may be screen 1050(FIG. 10F) in some embodiments. While event details screen 1110 isdisplayed, if a user makes contact with the touch-sensitive display ofdevice 500—and the contact has a maximum intensity exceeding athreshold—the calendar application may display options screen 1120.Options screen 1120 may be screen 920 (FIG. 9A) in some embodiments.Options screen 1120 may include: affordance 1122 for accepting theinvitation; affordance 1124 for declining the invitation; affordance1126 for indicating tentative attendance; and affordance 1128 forinitiating communication (e.g., e-mail or message) with a member of theinvitation, such as the event's organizer. If a user makes contact withaffordance 1122, the calendar application displays acceptance screen1130. Acceptance screen 1130 may show an indication confirming that thecalendar entry has been accepted. The calendar application also maytransmit a message to the event organizer indicating the user'sacceptance of the calendar entry.

In some embodiments, device 500 may display acceptance screen 1130momentarily (e.g., for a predetermined time interval), and subsequentlydisplay calendar inbox screen 1140. In some embodiments, device 500 maydisplay acceptance screen 1130 until a user input is received (e.g., atouch or swipe), at which time device 500 transitions to the display ofcalendar inbox screen 1140. While calendar inbox screens 1100 and 1140are similar, note that region 1102 is displayed below divider 1142 inscreen 1140. This positioning indicates that the user has responded tothe incoming calendar entry represented by affordance 1102. In this way,other invitations (e.g., the invitation represented by region 1144) maybe more prominently displayed to encourage user response.

5. Creating New Calendar Entries

Attention is now directed to the creation of new calendar entries usingthe calendar application. This aspect is described with respect to FIGS.12A and 12B. FIG. 12A illustrates exemplary user interface screens forcreating a new calendar entry according to some embodiments. As shown,device 500 may display day screen 1200, which may be screen 630 (FIG.6D) in some examples. While day screen 1200 is displayed, if a userselects position 1206, the calendar application may display new entryscreen 1210. New entry screen 1210 may include input areas for enteringinformation regarding the new calendar entry. For example, new entryscreen 1210 may include text input area 1212 for a name of thecorresponding event. Screen 1210 may also include affordance 1214 forinvoking a time (and optionally, day) picker for an event time. Screen1210 may also include affordance 1216 for entering location information.Screen 1210 also may include affordance 1218 for invoking a selector forselecting meeting attendees. In some examples, affordance 1214 maydefault to a meeting date of day 1204, which is the day displayed on dayscreen 1200. In some embodiments, affordance 1214 may default to a timecorresponding to position 1206, which is the location of user selection1202. In some embodiments, affordance 1214 may default to the top of thenext hour or to the next half hour.

FIG. 12B illustrates exemplary user interface screens for creating a newcalendar entry according to some embodiments. As shown, device 500 maydisplay day screen 1220, which may be screen 630 (FIG. 6D) in someembodiments. While day screen 1220 is displayed, if a user makes contact1222 with the touch-sensitive display of device 500, and acharacteristic intensity of the contact exceeds a threshold value, thecalendar application may display options screen 1230. Options screen1230 may include affordance 1232 for creating a new calendar entry.While options screen 1230 is displayed, if a user selects affordance1232, the calendar application may display new calendar entry screen1240. Screen 1240 may be new calendar entry screen 1210 in someembodiments.

6. Exemplary Flow: Contacting Organizer

Attention is now directed to features for contacting one or more personsassociated with calendar entry, such as an event organizer. This aspectis described with respect to FIGS. 13 and 14. As shown in FIG. 13,device 500 may display calendar inbox screen 1300. Calendar inbox screen1300 may be screen 930 (FIG. 9C) in some embodiments. Calendar inboxscreen 1300 may include region 1304 representing a calendar entry. Whena user selects region 1304, the calendar application may displaycalendar entry details screen 1310. Calendar entry details screen 1310may be screen 1050 (FIG. 10F) in some embodiments. Calendar entrydetails screen 1310 may have affordance 1312 identifying an eventorganizer. When a user selects affordance 1312, the calendar applicationmay display contact card screen 1320.

Contact card screen 1320 also may include name 1322, phone number 1324,and e-mail 1326 for the event organizer. When a user selects phonenumber 1322, the calendar application may initiate a phone call to theindicated number. In some embodiments, the phone call may be initiatedusing a cellular communication unit of device 500. In some embodiments,the phone call may be initiated using a network communication unit ofdevice 500, such as a voice-over-IP unit. In some embodiments, device500 instructs a companion device, such as a cellular phone, to initiatethe phone call using the companion device's cellular communication unit.In some embodiments, device 500 instructs a companion device, such as anetworkable laptop computer, to initiate the phone call using thecompanion device's network communication unit. Upon initiating the phonecall, device 500 displays call progress screen 1330. At the conclusionof the phone call, device 500 returns to event details screen 1310.

FIG. 14A shows additional exemplary user interface screens forcontacting one or more persons associated with a calendar entry. Asshown, device 500 may display calendar entry details screen 1400.Calendar entry details screen 1400 may be screen 1050 (FIG. 6F) in someembodiments. Calendar entry details screen 1400 may include affordance1402 identifying the event's organizer. If a user selects eventorganizer affordance 1402, the calendar application may display contactcard screen 1410.

Contact card screen 1410 may include affordance 1412 for initiating aphone call to the event organizer. If a user selects affordance 1412,device 500 may display screen 1330 (FIG. 13) and initiate a call to theorganizer. Contact card screen 1410 also may include affordance 1420 forinitiating a video conference with the event organizer. If a userselects affordance 1412, device 500 may launch a video conferencingapplication.

Contact card screen 1410 also may include affordance 1414 for initiatingan e-mail to the event organizer. If a user selects affordance 1414,device 500 may permit a user to create an e-mail message using variousmodalities. In some embodiments, device 500 may display a soft keyboardfor entering an e-mail message. In some embodiments, device 500 maypermit a user to aurally dictate a message which is then included in adraft e-mail as text. In some embodiments, device 500 may permit a userto record a voice memo, which is then included in a draft e-mail as anaudio attachment. In some embodiments, device 500 may permit a user tosend emoji characters. In some embodiments, device 500 may present, forthe user's selection, a list of predicted text that device 500 hasdetermined to be possible and/or likely responses.

These predicted texts may include those described in U.S. ProvisionalPatent Application No. 62/005,958, “Canned Answers in Messages,” filedMay 30, 2014, (the “Canned Answers Specification”) the content of whichis hereby incorporated by reference. For instance, the Canned AnswersSpecification describes predicting a user's likely response to anincoming message and presenting those predicted responses as options foruser selection. In some embodiments the predictions are based thecontent of an incoming message and/or the sender's identity. In someexamples, responsive to an incoming message that contains a questionmark, the system predicts and presents the canned answers “yes” and“no.” In some examples, responsive to an incoming message that containstwo phrases separated by the word “or,” the system presents the wordappearing before “or” and the word appearing after “or” as cannedanswers. In some examples, responsive to an incoming message from asender identified as the user's wife (e.g., through the user's contactlist), the system predicts and presents the phrase “I love you” as acanned response.

Contact card screen 1410 may also include affordance 1418 for sending amessage to the event organizer. Device 500 may permit a user to create amessage (e.g., SMS message) using one or more of the above-describedinput modalities.

Contact card screen 1410 also may include affordance 1416 for launchinga map application that maps an address of the event organizer. If a userselects affordance 1416, device 500 may launch a maps applicationmapping the address of the event organizer. In some embodiments, theaddress is static, such as a work address from the organizer's businesscard. In some embodiments, the address is dynamic, such as updatedlocational information reported by a GPS-equipped device of theorganizer's.

FIG. 14B shows additional exemplary user interface screens for an eventreminder. As shown, device 500 may display event reminder screen 1450,for instance, alerting the user of an upcoming event. As previouslydescribed, in some examples, the device 500 may alert the user an amountof time prior to an event, and the amount of time may either be fixed orbased on an amount of time required for the user to travel to the event.Event reminder screen 1450 may include affordance 1452 identifying theevent, affordance 1454 identifying the location of the event, affordance1456 identifying the time of the event, and affordance 1458 identifyingthe location of the event. In some examples, any of affordances1452-1458 may be combined or separated further into sub-affordances. Theevent reminder screen 1450 may further include affordances 1460 and1462. If a user selects affordance 1460, the calendar application maydisplay a contact card screen, such as the contact card screen 1410(FIG. 14A), allowing the user to contact the organizer as described. Theuser may, for instance, indicate to the organizer a time at which theuser will arrive at the event. If a user selects affordance 1462, thecalendar application may launch a map application that maps an addressof the event (or event organizer). As described, in some examples, theaddress may be static or dynamic.

7. Additional Details—Calendar Screens

Attention is now directed to additional user interface transitions thatmay be displayed by the calendar application in response to userinteraction. FIG. 15 illustrates an exemplary transition between theyear and month screens in some embodiments of the calendar application.As shown, device 500 may display year screen 1500 showing certain monthsof the year. Year screen 1500 may be screen 610 (FIG. 6B) in someembodiments. A user may select one of the displayed months. For example,a user may contact the touchscreen at position 1502 corresponding to themonth of September. In response to the user selection, the calendarapplication transitions to month screen 1510 showing the touched month(i.e., September). Month screen 1510 may be month screen 600 (FIG. 6A)in some embodiments. As shown, the transition may include enlarging (atleast parts of) the selected month (i.e., September) from screen 1500into screen 1520. In some embodiments, the transition includestranslating the non-selected months—displayed in screen 1500—off-screenas the selected month enlarges.

FIG. 16 illustrates another exemplary transition between the year andmonth screens in some embodiments of the calendar application. As shown,device 500 may display year screen 1600 showing certain months of theyears 2017 and 2018. Year screen 1600 may be screen 610 (FIG. 6B) insome examples. While year screen 1600 is displayed, a user may swipeupwards on the touch-sensitive display of device 500, which may causethe calendar application to scroll the year screen 1600 in acorresponding direction to reveal additional months in year 2018. Yearscreen 1610 illustrates the display of additional months of the year2018. In year screen 1610, the month of August is the center-most of thedisplayed months. A user may rotate the rotatable input mechanism ofdevice 500 while year screen 1610 is displayed with August being thecenter-most month. In response to rotation 1614, the calendarapplication may transition to month screen 1620 displaying details ofthe center-most month—August. In some embodiments, the transitionincludes enlarging (at least parts of) the display of the center-mostmonth. In some embodiments, the transition includes translating theother displayed months off-screen as the center-most month expands.

FIG. 17 illustrates another exemplary transition between the year andmonth screens in some embodiments of the calendar application. As shown,device 500 may display year screen 1700. Year screen 1700 may be yearscreen 610 (FIG. 6B) in some embodiments. When year screen 1700 isdisplayed, a user may select one of the displayed months. For example, auser may touch the touch-sensitive display of device 500 at a positionwhere month 1702 (i.e., December) is displayed. In some embodiments, inresponse to the user selection, the selected month (1702) is visuallyemphasized. For example, the selected month may brighten, flash, becomeboldfaced, and/or become more opaque. In some embodiments, in responseto the user selection, the non-selected months are visuallyde-emphasized. For example, they may dim, fade, and/or becometranslucent. In some embodiments, the selected month remains unchangedvisually while the non-selected months are visually de-emphasized. Insome embodiments, the selected month is visually emphasized while thenon-selected months remain unchanged visually.

While still selecting (e.g., touching) the touch-sensitive display ofdevice 500, the user may drag (e.g., slide) his finger in a particulardirection, for example, upwards. As shown, in response to the upwardsliding finger, month 1704 (November)—which precedes month 1702(December)—becomes visually emphasized, and month 1702 becomes visuallyde-emphasized. As the user continues to slide his finger upwards, month1706 (October)—which precedes month 1704 (November)—becomes visuallyemphasized, and month 1702 becomes visually de-emphasized. When the userreleases his selection (e.g., touch), all of the displayed months mayreturn to their normal visual appearance, except month 1706 (October),which now has focus. In this way, a user can place focus on a particularmonth of the displayed year. While month 1706 has focus, a user mayrotate the rotatable input mechanism of device 500 (as indicated byarrow 1708) to transition from year screen 1730 to month screen 1740,which shows the days of month 1706.

FIG. 18 illustrates an exemplary transition between the month and dayscreens of the calendar application. As shown, device 500 may displaymonth screen 1800. Month screen 1800 may be screen 600 (FIG. 6A) in someexamples. Month screen includes affordance 1802 indicating a currentlyselected day. While month screen 1800 is displayed, a user may rotatethe rotatable input mechanism of device 500, as indicated by arrow 1802.In response to rotation 1802, the calendar application may transition tothe display of day view 1810. Day view 1810 may display calendar entriesscheduled for the day marked by affordance 1804.

FIG. 19 illustrates an exemplary transition between the month and weekscreens of the calendar application. The week screen displays the daysin a particular week. As shown, device 500 may display month screen1900. Month screen 1900 may be screen 600 (FIG. 6A) in some embodiments.Month screen 1900 may indicate the days of a month across multiple rows.These rows include, for example, row 1904, which indicates the days of aparticular week in the displayed month. While month screen 1900 isdisplayed, a user may rotate the rotatable input mechanism of device 500as indicated by arrow 1902. In response to rotation 1902, device 500 maytransition from displaying month screen 1900 to displaying week screen1930. In week screen 1930, numerals representing the days of a week aredisplayed vertically. In addition, weekday identifiers (e.g., Mon, Tues,so forth) are displayed adjacent the numerals.

The translation between screen 1900 and screen 1930 involves on-screentranslation of numerals (representing days) from their positions in row1904 to their new positions in column 1932. This transition isillustrated by exemplary screens 1910 and 1920. In screen 1910, row 1904is shown pivoting from its horizontal (row) orientation towards avertical (column) orientation roughly about position 1912. While row1904 pivots, numerals in other rows are translated off-screen. Screen1920 illustrates further progression of this translation. As can beseen, in this stage of the transition, many numerals have beentranslated off-screen, leaving primarily the numerals of row 1904. Asthe transition of row 1904 into column 1932 completes, weekdayidentifiers are added adjacent the displayed numerals, as shown on weekscreen 1930.

FIGS. 20A and 20B illustrate a feature of the calendar application thatmay be referred to as progressive disclosure. Progressive disclosurerefers to the ability of the application to vary—as a user zooms in orout—the content of displayed information. Progressive disclosure mayoccur together with changes in the size of the displayed information, asa user invokes zooming functionality. In some embodiments, device 500may display more detailed information regarding displayed events whenfewer events are displayed (e.g., when a calendar screen is zoomed in).Conversely, device 500 may display less information regarding specificevents when more events are displayed (e.g., when a calendar applicationis zoomed out). In this way, the calendar application may display themost appropriate level of detail based on the granularity of the zoom.It is noted that progressive disclosure, which may display moreinformation when zoomed-in, stands in contrast to conventional zoomfunctionalities, which tend to display less information, at a largersize, when zoomed-in.

Exemplary user interface screens illustrating progressive disclosure arenow described. As shown in FIG. 20A, device 500 may display day screen2000. Day screen 2000 may be screen 630 (FIG. 6D) in some embodiments.Day screen 2000 includes calendar entries scheduled for day 2002. Device500 may respond to user input representing request(s) to zoom. In someembodiments, a user may pinch and/or de-pinch day screen 2000 to zoomout and zoom in, respectively. In some embodiments, a user may rotatethe rotational input mechanism of device 500 to zoom (as shown byrotational input 2022).

As illustrated in FIG. 20A, if a user provides input representing arequest to zoom-in while day screen 2000 is displayed, device maydisplay day screen 2010 which shows fewer hours of day 2002 but showsmore information about calendar entries scheduled during the displayedhours (e.g., entry 2006). The request to zoom-in may be provided using atouch gesture (e.g., de-pinching) in some embodiments. The request tozoom-in may be provided using a rotation (2022) of a rotatable inputmechanism of device 500 in some embodiments.

Turning to FIG. 20B, a user also may provide input representing arequest to zoom-out while day screen 2000 is displayed. When thisoccurs, device 500 may transition to an intermediate, multi-day screen2020 which displays calendar entries for multiple days. As shown, screen2020 includes regions 2022, 2024, and 2026 representing calendar entrieson for different days. The size (e.g., height) of regions 2022, 2024,and 2026 are proportional to the length of the corresponding calendarentries. While multi-day screen 2020 is displayed, a user may furtherzoom out to multi-month screen 2030, where calendar entries acrossmultiple months are displayed using affordances, in this example, lines.In screen 2030, lines 2032 indicate the presence of scheduled events inthe displayed months, but the size of lines 2032 may not representdurations. While multi-month screen 2030 is displayed, a user mayfurther zoom out to multi-year screen 2040, where numbers of scheduledcalendar entries per year are tallied. For example, as shown by text2042, three calendar entries are scheduled in the year of 2019. Note,although not shown, it is possible to transition from screen 2000 toscreens 2020, 2030, and 2040 through one or more rotations of arotatable input mechanism of device 500.

Attention is now directed to other exemplary user interface screens fordisplaying calendar information for a particular day and a particularyear. FIG. 21 illustrates exemplary day screen 2100, which may be usedin some embodiments to indicate calendar entries scheduled for aparticular day. Day screen 2100 includes day-date indicator 2102. Dayscreen 2100 also includes one or more arc-shaped affordances (e.g., 2104and 2106) indicating calendar entries scheduled for the day. The endpoints of the arc-shaped affordances may indicate start and end times ofcorresponding calendar entries. For example, the left end of affordance2104 may indicate the start of a calendar entry and the right end ofaffordance 2104 may indicate the end of the event. The affordances maybe aligned based on the traditional layout of time markers on a circularwatch face. That is, affordance 2104 corresponds to an event scheduledfrom noon to one o'clock. Also, as a result of this circular alignment,arc-shaped affordances 2104 and 2106 may be arranged circumferentiallyaround day-date indicator 2102.

In addition, FIG. 21 illustrates exemplary year screen 2110, which maybe used in some embodiments to indicate calendar entries for aparticular year. Year screen 2110 includes month indicators 2112 and2114. Year screen 2110 also includes line segments (e.g., 2116, 2118)indicating the presence of calendar entries during the month. The lengthof a line segment may indicate the length of the corresponding calendarentry. For example, the length of line 2116 (which is relativelyshorter) may indicate a day-long event during month 2112 while thelength of line 2118 (which is relatively longer) may indicate aweek-long event during month 2114.

Attention is now directed to an exemplary transition between the dayscreen and the inbox screen of the calendar application in someembodiments. As shown in FIG. 22, device 10 may display day screen 2200.Day screen 2200 may be day screen 630 (FIG. 6D) or day screen 640 (FIG.6E) in some embodiments. A user may drag (e.g., by way of a touchgesture such as a swipe) day screen 2200 to reveal calendar inbox screen2210. Calendar inbox screen 2210 may be screen 930 (FIG. 9C) in someembodiments. Alternatively, a user may rotate the rotatable inputmechanism of device 500 to transition between day screen 2200 andcalendar inbox screen 2210. Day screen 2200 and calendar inbox screen2210 may each include affordances 2201 and 2202 indicating the positionof each screen among a plurality of screens. An exemplary implementationof affordances 2201 and 2202 is paging dots. Affordances 2201 and 2202may enlarge, darken, or otherwise change in visual appearance when thecorresponding calendar inbox screen is displayed.

While day screen 2200 is displayed, a user may contact (e.g., touch) thetouch-sensitive display of device 500. Device 500 may determine orotherwise obtain a measurement of the intensity of the contact. If theintensity is above the threshold, the calendar application may causedevice 500 to display options screen 2220. Options screen 2220 may bescreens 992 (FIG. 9F), 1000 (FIG. 10A), 1010 (FIG. 10B), 1020 (FIG.10C), 1030 (FIG. 10D), or 1040 (FIG. 10E) in some embodiments. If theintensity is below a threshold, the calendar application may causedevice 500 to display, for example, the details of an event that isshown on screen 2200.

While calendar inbox screen 2210 is displayed, a user may contact (e.g.,touch) the touch-sensitive display of device 500. Device 500 maydetermine or otherwise obtain a measurement of the intensity of thecontact. If the intensity is above the threshold, the calendarapplication may cause device 500 to display options screen 2230. Optionsscreen 2220 may be screens 992 (FIG. 9F), 1000 (FIG. 10A), 1010 (FIG.10B), 1020 (FIG. 10C), 1030 (FIG. 10D), or 1040 (FIG. 10E) in someembodiments. If the intensity is below a threshold, the calendarapplication may cause device 500 to display, for example, the details ofan event that is shown on screen 2210.

Attention is now directed to another exemplary landing screen 2310 forthe calendar application, an example of which is shown in FIG. 23. Asshown, device 500 may display user interface screen 2300 having icon2302. Icon 2302 may correspond to the calendar application. In responseto a selection of icon 2302, device 500 may launch the calendarapplication, meaning that the calendar application is brought to theforeground of the touch-sensitive display of device 500. In someembodiments, the selection may be performed via a touch gesture (e.g.,tap, touch and hold, swipe, flick) on icon 2302. In some embodiments,the selection may be performed via rotation 2304 of a rotatable inputmechanism of device 500. Upon launching, calendar application causesdevice 500 to display landing screen 2310. Exemplary landing screen 2310includes affordance 2312 for invoking a day screen showing calendarentries for the current day. Day screen may be screen 1030 (FIG. 10D) or1040 (FIG. 10E) in some embodiments. Exemplary landing screen 2310 alsoincludes affordance 2313 for invoking a calendar inbox screen 2330.Calendar inbox screen 2330 may be screen 930 (FIG. 9B) or screens 950and 952 (FIG. 9C) in some embodiments.

8. Exemplary Processes

Attention is now directed to exemplary processes for carrying out theuser interface techniques described above. FIG. 24 depicts process 2400for displaying some of the above-described user interfaces. Process 2400may be performed at an electronic device with a touch-sensitive displayand a rotatable input mechanism, like device 500 (FIG. 5). At block2402, the device may display, on its touch-sensitive display, an iconrepresenting a calendar application. At block 2404, the device maydetect user input. At block 2406, the device may determine whether thedetected user input represents a touch on the displayed icon or amovement of the rotatable input mechanism. At block 2408, in response toa determination that the detected user input represents a touch on thedisplayed icon, the device may launch the calendar application andtransition from the display of the icon, through at least oneintermediate user interface screen, to displaying a landing screen ofthe calendar application. Optionally, the transition from theintermediate user interaction screen to the landing screen may occurafter the intermediate user interaction screen has been displayed for apredetermined amount of time. At block 2410, in response to adetermination that the detected user input represents movement of therotatable input mechanism, the device may launch the calendarapplication and transitioning from the display of the icon directly todisplaying the landing screen of the calendar application.

In some embodiments, the transition at block 2408 involves the displayof a year screen (e.g., screen 610; FIG. 6B) and a month screen (e.g.,screen 600; FIG. 6A) before landing on a day screen (e.g., screen 630;FIG. 6D). In some embodiments, the transition at block 2410 involvesreplacing the display of the icon directly with the display of a dayscreen (e.g., screen 630; FIG. 6D) without the display of additionalintermediate screens. The device may thus provide the user with morecontext if the user interacts with the device in one way (e.g., touch onthe application icon), and the device may provide the user with quickeraccess to the day screen if the user interacts with the device inanother way (e.g., rotation of an input mechanism).

When displaying the day screen, device 500 may display one or moreaffordances representing calendar entries scheduled for the day. Theaffordances may have the visual appearance of a geometric shape, such asa rectangle. More generally speaking, the affordances may be regions ofthe display that are distinguishable from the background of the calendarapplication. Optionally, when the landing screen is the day screen,device 500 may display calendar entries for the current day. Optionally,when the month screen is displayed, device 500 may display an indicator(e.g., numeral) indicating the current day towards the vertical centerof the display.

FIG. 25 depicts process 2500 for displaying some of the above-describeduser interfaces. Process 2500 may be performed at an electronic devicewith a touch-sensitive display and a rotatable input mechanism, likedevice 500 (FIG. 5). At block 2502, the device may display, on itstouch-sensitive display, an affordance representing a calendarapplication. At block 2504, the device may detect user input. At block2506, the device may determine whether the user input is a touch on thedisplayed affordance or a movement of the rotatable input mechanism. Atblock 2508, in accordance with a determination that the detected userinput is a touch on the displayed affordance, the device may: (i)display a first text indicating at least two months in a year (e.g.,year screen); (ii) then, replace the display of the first text with adisplay of a second text indicating at least some days in one and onlyone month of the year (e.g., month screen); and (iii) then, replace thedisplay of the second text with a display of at least one affordancerepresenting at least one calendar entry (e.g., day screen). At block2510, in accordance with a determination that the detected user input isa movement of the rotatable input mechanism, the device may display atleast one affordance representing at least one calendar entry (e.g., dayscreen). At block 2512, in response to an additional rotation of therotatable mechanism, the device may replace the display of the at leastone calendar entry with a display of a second text indicating at leastsome days in one and only one month of the year (e.g., month screen). Atblock 2514, in response to an additional rotation of the rotatablemechanism, the device may replace the display of the second text withthe first text indicating at least two months in a year (e.g., yearscreen).

FIG. 26 depicts process 2600 for displaying some of the above-describeduser interfaces. Process 2600 may be performed at an electronic devicewith a touch-sensitive display and a rotatable input mechanism, likedevice 500 (FIG. 5). At block 2602, the device may display, on itstouch-sensitive display, an affordance representing a calendarapplication. At block 2604, the device may detect user input. At block2606, the device may determine whether the user input is a touch on thedisplayed affordance or a rotation of the rotatable input mechanism. Atblock 2608, in accordance with a determination that the detected userinput is a touch on the displayed affordance, the device may: (i)display a first text indicating at least two months in a year (e.g.,year screen); (ii) then, replace the display of the first text with adisplay of a second text indicating at least some days in one and onlyone month of the year (e.g., month screen); and (iii) then replace thedisplay of the second text with a display of at least one affordancerepresenting at least one calendar entry (e.g., day screen). At block2610, in accordance with a determination that the detected user input isa movement of the rotatable input mechanism, the device may display thefirst text indicating at least two months in a year (e.g., year screen).At block 2612, in response to an additional rotation of the rotatablemechanism, the device may replace the display of the first text with adisplay of the second text indicating at least some days in one and onlyone month of the year (e.g., month screen). At block 2614, in responseto an additional rotation of the rotatable mechanism, the device mayreplace the display of the second text with a display of at least oneaffordance representing at least one calendar entry (e.g., day screen).

The ability of the device to provide multiple navigational paths isbeneficial in that it permits a user to invoke the most suitable devicebehavior for particular usage cases. The ability is also beneficial inbattery operated devices in that short-cutting through intermediate userinterface screens can reduce processor drain thereby conserving batterylife.

FIG. 27 depicts process 2700 for displaying additional calendarapplication features. Process 2700 may be performed at an electronicdevice with a touch-sensitive display, where the touch-sensitive displaycomprises one or more sensors to detect the intensity of contacts withthe touch-sensitive display. At block 2702, the device may display anaffordance representing a calendar entry in a calendar application. Atblock 2704, the device may detect a touch on the display, the touchhaving a characteristic intensity, the touch located at the displayeduser interface object representing the calendar entry. At block 2706,the device may determine whether the characteristic intensity of thetouch is below a threshold intensity. At block 2708, in response to adetermination that the characteristic intensity of the touch is belowthe threshold intensity, the device may display a time and a locationassociated with the calendar entry. At block 2710, in response to adetermination that the characteristic intensity of the touch is notbelow the threshold intensity, the device may display, on thetouch-sensitive display, a plurality of affordances representingfunctions of the calendar application.

Optionally, the displayed affordances may include an affordance forinitiating a phone call to a contact that is associated with thecalendar entry, such as an event organizer. Optionally, the displayedaffordances may include an affordance for initiating an e-mail draft tothe contact. The phone call and the e-mail draft may be initiated ondevice 500, or device 500 may instruct a companion device, such as acellular phone or a laptop computer, to initiate the phone call and/orthe e-mail draft.

FIG. 28 depicts process 2800 for displaying additional calendarapplication features. Process 2800 may be performed at an electronicdevice with a touch-sensitive display. At block 2802, the device maydisplay, on its touch-sensitive display, a plurality of calendarentries. The plurality of calendar entries may include a first calendarentry and a second calendar entry. The first calendar entry may bedisplayed above the second calendar entry. At block 2804, the device mayreceive user input representing user acceptance of the first calendarentry. At block 2806, in response to receiving the user input, thedevice may display the first calendar entry below the second calendarentry.

Optionally, at block 2804, the device may detect a touch on thetouch-sensitive display having a characteristic intensity, where thetouch has a characteristic intensity. The device may determine whetherthe characteristic intensity is above a threshold intensity. The devicemay, in response to a determination that the characteristic intensity isabove the threshold intensity, display an accept affordance foraccepting the calendar entry and a decline affordance for declining thecalendar entry. The device may detect a user selection of the acceptaffordance.

Optionally, at block 2804, the device may detect a user selection of thefirst calendar entry. In response to detecting the user selection of thefirst calendar entry, the device may: (i) display a time and location ofthe calendar entry; and (ii) display an accept affordance for acceptingthe calendar entry. Further, the device may detect a user selection ofthe accept affordance.

FIG. 29 depicts process 2900 for displaying additional calendarapplication features. Process 2900 may be performed at an electronicdevice with a touch-sensitive display. At block 2902, the device maydisplay, on the touch-sensitive display, a first user interface screenhaving a plurality of calendar entries. At block 2904, the device mayreceive first data representing user acceptance of a first calendarentry of the plurality of calendar entries. At block 2906, the devicemay, in response to receiving the first data, remove the accepted firstcalendar entry from the first user interface screen. At block 2908, thedevice may receive second data representing a user input. The input maybe a swipe on the touch-sensitive display in some examples. The userinput may be a movement of a rotatable input mechanism of the device insome examples. At block 2910, the device may, in response to receivingthe second data, replace the display of the first user interface screenwith a display of a second user interface screen having a plurality ofaccepted calendar entries.

FIG. 30 depicts process 3000 for selecting a month to focus onto when anumber of months are being displayed (e.g., in a year screen). Process3000 may be performed at an electronic device with a touch-sensitivedisplay. At block 3002, the device may display a user interface screenon the touch-sensitive display. The displayed user interface screen mayinclude a plurality of texts indicating a plurality of months in a year.The texts of the plurality of texts may be organized according to alayout having at least two rows and at least two columns. The pluralityof texts may have an initial visual characteristic. At block 3004, thedevice detects a user selection of a first text of the plurality oftexts, the first text indicating a first month of the plurality ofmonths. In some embodiments, the user selection may be a touch contactat a display position of the first month. At block 3006, in response todetecting the user selection, the device may change the visualcharacteristic of the plurality of texts except the first textindicating the first month. At block 3008, the device may detect amovement of the user selection of the first text. At block 3010, inresponse to detecting the movement, the device may: (i) change thevisual characteristic of the first text indicating the first month, and(ii) return the visual characteristic of a second text indicating asecond month of the plurality of months to its initial visualcharacteristic. In some embodiments, the movement may be a drag of thetouch contact. Further, in some examples, changing the visualcharacteristic may involve dimming, greying, darkening, makingtranslucent, or another technique for visually de-emphasizinginformation. At block 3012, the device may detect a removal of the userselection. In some embodiments, the removal may be a touch lift-off(also called touch release). At block 3014, in response to the removalof the user selection, designate the second month as having focus.

FIG. 31 depicts process 3100 for transitioning between a month screenand a week screen. Process 3100 may be performed at an electronic devicewith a touch-sensitive display. At block 3102, the device may display arow of numerals, the numerals indicating days in a month. At block 3104,the device may detect user input. At block 3106, the device may, inresponse to detecting the user input, translate all but one of thedisplayed numerals from its respective position in the row into a newposition. The displayed numerals, in their new positions, may form acolumn of numerals. The displayed numerals may represent a given week ofthe month. As part of the translation at block 3106, the device maytranslate off-screen (and cease to display) numerals representing daysoutside the given week.

FIG. 32 depicts process 3200 for transitioning between a month screenand a week screen. Process 3200 may be performed at an electronic devicewith a touch-sensitive display. At block 3202, the device may display onits touch-sensitive display: (i) text indicating hours in a day; (ii) atleast one region representing a calendar entry scheduled during theindicated hours; and (iii) text inside the at least one regionindicating a name of the calendar entry. At block 3204, the device maydetect user input representing a zoom-in or zoom-out command. At block3206, in accordance with a determination that the user input representsa zoom-in command, the device may: (i) enlarge the at least one region;and (ii) display additional text inside the at least one regionindicating details of the calendar entry. The user input may be ade-pinching gesture in some examples. The user input may be a rotationof a rotatable input mechanism of the device in some examples. At block3208, in accordance with a determination that the user input representsa zoom-out command, the device may: (i) remove the display of the textindicating days of the month and the user interface object; (ii) reducethe size of the at least one region representing a calendar entry;and/or (iii) displaying a count of calendar entries within a timeinterval.

FIG. 33 depicts process 3300 for transitioning between a month screenand a week screen. Process 3300 may be performed at an electronic devicewith a touch-sensitive display. At block 3302, the device may display onits touch-sensitive display, an application affordance representing acalendar application. At block 3304, the device may detect a userselection of the application affordance. At block 3306, in response todetecting the user selection of the application affordance, the devicemay: (i) launch the calendar application; (ii) display a first eventaffordance representing a first calendar entry; and (iii) display asecond event affordance representing a second calendar entry. The secondcalendar entry may be longer in duration than the first calendar entryeven if the size of the first event affordance is larger than the sizeof the second event affordance. In this way, device 500 may display anall-day calendar entry is as the second calendar entry. At block 3308,the device may detect user selection of the second event affordance. Atblock 3310, in response to detecting the user selection of the secondevent affordance, the device may enlarge the second affordance.Optionally, at block 3310, the device may display additional informationregarding the calendar entry represented by the second affordance. Theadditional information may include, for example, a name and locationassociated with the all-day calendar entry.

FIG. 34 shows exemplary functional blocks of an electronic device 3400that, in some embodiments, perform the features described above. Asshown in FIG. 34, an electronic device 3400 includes a display unit 3402configured to display graphical objects; a input/output (I/O) unit 3404configured to receive user gestures; one or more sensor units 3406configured to detect intensity of contacts with the touch-sensitivesurface unit; communications unit 3408 and a processing unit 3410coupled to the display unit 3402, the I/O unit 3404, the sensor units3406, and communication unit 3408. The processing unit may include agraphics processing unit 3412 and a calendar management unit 3414. Thefunctional blocks of the device 3400 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 34 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

In some embodiments, processing unit 3408 is configured to detect a userinput (e.g., detecting a touch gesture or other button input with thedetecting unit 3410) on a graphical user interface object, and displayrelevant calendar information in accordance with the calendarinstruction.

For example, in some embodiments, in response to a touch on a calendar,application icon, graphics processing unit 3412 will cause display unit3402 to display a sequence of user interface screens (e.g., year screen,to month screen, to day screen). As another example, in someembodiments, in response to a movement of a rotatable input mechanism,graphics processing unit 3412 will cause display unit 3402 to displayingcycle through the display of individual user interface screens (e.g.,year screen, month screen, day screen). Calendar management unit 3414may identify relevant information to be displayed on each screen. Insome embodiments, calendar management unit 3414 may progressivelypresent an increasing amount of information to a user as the userfocuses on a particular day's activities.

As yet another example, in some embodiments, input/output unit 3404 maybe able to determine the intensities of touch contacts. In response to ahigh-intensity contact, graphics processing unit 3412 may cause displayunit 3402 to present additional user interface features. For instance, auser may able to invoke graphical user interface affordances foraccepting or declining calendar invitations using a high-intensitycontact(s). A user may also be able to invoke graphical user interfaceaffordances for contacting (e.g., e-mailing and/or calling) othermembers of a calendar entry, such as an event organizer associated withthe calendar entry.

As still yet another example, in some embodiments, calendar managementunit 3414 may maintain a list of calendar entries that a user hasresponded to and those that the user has not responded to. Calendarmanagement unit 3414, in conjunction with graphics processing unit 3412,may cause display unit 3402 to present calendar entries that stillrequire a user's response in one region of the user interface screen,and to present calendar entries that the user has already dealt with inanother region.

As still yet another example, in some embodiments, graphics processingunit 3412 will cause display unit 3402 to visually emphasize andde-emphasized displayed days, months, and/or years. Calendar managementunit 3414 may recognize a visually emphasized day/month/year as beinginformation that is relevant to the user. For instance, a user may useone input modality (e.g., touch) to emphasize a particular month amongdisplayed months, and use another input modality (e.g., movement of arotatable input mechanism) to retrieve more information about theparticular month.

In accordance with some embodiments, FIG. 35 shows a functional blockdiagram of an electronic device 3500 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 35 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 35, an electronic device 3500 includes a display unit3502 configured to display a graphic user interface, a touch sensitivesurface unit 3504 configured to receive contacts, and a processing unit3506 coupled to the display unit 3502 and the touch-sensitive surfaceunit 3504. In some embodiments, the processing unit 3506 includes adisplay enabling unit 3508, a detecting unit 3510, a launching unit3512, a transitioning unit 3514, and, optionally, a determining unit3516.

The processing unit 3506 is configured to enable display (e.g., with thedisplay enabling unit 3508) of, on the display unit 3502, an iconrepresenting a calendar application; detect (e.g., with the detectingunit 3510) user input; in response to a determination that the detecteduser input represents a touch on the displayed icon, launch (e.g., withthe launching unit 3512) the calendar application and transition (e.g.,with the transitioning unit 3514) from the display of the icon, throughat least one intermediate user interface screen, to enable display of alanding screen of the calendar application; and in response to adetermination that the detected user input represents movement of arotatable input mechanism, launch (e.g., with the launching unit 3512)the calendar application and transitioning from the display of the icondirectly to enable display of the landing screen of the calendarapplication.

In some embodiments, enabling display of the landing screen of thecalendar application comprises enabling display of at least one calendarentry scheduled for the current day.

In some embodiments, transitioning through the at least one intermediateuser interface screen comprises enabling display of an intermediate userinterface screen having text representing at least some days of thecurrent month.

In some embodiments, the user input is a first user input representing afirst movement of the rotatable input mechanism, and the processing unit3506 is further configured to detect (e.g., with the detecting unit3510) a second user input representing a second movement of therotatable movement mechanism; and in response to detecting the seconduser input, enable display (e.g., with the display enabling unit 3508)of text representing at least some days of the current month.

In some embodiments, the processing unit 3506 is further configured toenable display (e.g., with the display enabling unit 3508) of anindicator indicating the current day in the current month.

In some embodiments, enabling display of the icon representing thecalendar application comprises enabling display of a plurality of othericons representing other software applications and enabling display ofthe icon representing the calendar application as the center-most iconon-screen among the displayed icons.

In some embodiments, enabling display of the text that represents thecurrent day in the current month comprises enabling display of the textsubstantially centered on-screen in the vertical direction.

In some embodiments, the processing unit 3506 is further configured todetect (e.g., with the detecting unit 3510) user selection of a calendarentry of the at least one calendar entry scheduled for the current day,and in response to detecting user selection of the calendar entry,enable display (e.g., with the display enabling unit 3508) of a time andlocation of the selected calendar entry.

In some embodiments, the processing unit 3506 is further configured todetect (e.g., with the detecting unit 3510) a touch on thetouch-sensitive surface unit 3504 while enabling display of the time andlocation of the selected calendar entry, the touch having acharacteristic intensity; determine (e.g., with the determining unit3516) whether the characteristic intensity of the touch is above athreshold intensity; and in response to a determination that thecharacteristic intensity of the touch is above the threshold intensity,enable display (e.g., with the display enabling unit 3508) of, on thedisplay unit 3502, an affordance for accepting the calendar entry.

In some embodiments, the processing unit 3506 is further configured to,in response to a determination that the characteristic intensity of thetouch is not above the threshold intensity, enable display (e.g., withthe display enabling unit 3508) of additional information regarding theselected calendar entry.

In some embodiments, enabling display of at least one calendar entryscheduled for the current day comprises enabling display of at least oneaffordance representing the at least one calendar entries scheduled forthe current day; detecting user input representing a zoom-in command;and in response to detecting the user input representing the zoom-incommand, enlarging the at least one affordance, and enabling display ofadditional text inside the at least one affordance indicating details ofat least one represented calendar entry.

In some embodiments, enabling display of at least one calendar entryscheduled for the current day comprises enabling display of anaffordance representing at least two calendar entries scheduled for thecurrent day; detecting user input on the displayed affordance; and inresponse to detecting the user input on the displayed affordance,enabling display of at least two affordances representing the at leasttwo calendar entries.

In some embodiments, enabling display of additional text comprisesenabling display of calendar entry information selected from the groupconsisting of calendar entry time, location, and organizer.

In some embodiments, the affordance representing the calendarapplication is a contiguous region visually distinguishable from abackground of the calendar application.

The operations described above with reference to FIG. 24 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.35. For example, displaying operation 2402, detecting operation 2404,determining operation 2406, and launching operations 2408 and 2410 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 36 shows a functional blockdiagram of an electronic device 3600 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 36 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 36, an electronic device 3600 includes a display unit3602 configured to display a graphic user interface, a touch sensitivesurface unit 3604 configured to receive contacts, and a processing unit3606 coupled to the display unit 3602 and the touch-sensitive surfaceunit 3604. In some embodiments, the processing unit 3606 includes adisplay enabling unit 3608, a detecting unit 3610 and a replacing unit3612.

The processing unit 3606 is configured to enable display (e.g., with thedisplay enabling unit 3608) of, on the display unit 3602, an affordancerepresenting a calendar application; detect (e.g., with the detectingunit 3610) user input; in response to detecting the user input, (a) inaccordance with a determination that the detected user input is a touchon the displayed affordance: enable display (e.g., with the displayenabling unit 3608) of a first text indicating at least two months in ayear, then, replace (e.g., with the replacing unit 3612) the display ofthe first text with a display of a second text indicating at least somedays in one and only one month of the year, and then, replace (e.g.,with the replacing unit 3612) the display of the second text with adisplay of at least one affordance representing at least one calendarentry; and (b) in accordance with a determination that the detected userinput is a movement of a rotatable input mechanism: enable display(e.g., with the display enabling unit 3608) of at least one affordancerepresenting at least one calendar entry.

In some embodiments, the movement of the rotatable input mechanism is afirst movement of the rotatable input mechanism, the processing unit3606 further configured to detect (e.g., with the detecting unit 3610) asecond movement of the rotatable input mechanism; and in response todetecting the second movement, replace (e.g., with the replacing unit3612) the display of the at least one affordance representing the atleast one calendar entry with a display of the second text indicatingthe at least some days in the one and only one month of the year.

In some embodiments, the processing unit 3606 is further configured todetect (e.g., with the detecting unit 3610) a third movement of therotatable input mechanism; and in response to detecting the thirdmovement, replace (e.g., with the replacing unit 3612) the display ofthe second text with a display of the first text indicating the at leasttwo months in the year.

In some embodiments, replacing the display of the first text with thesecond text occurs automatically after the first text is displayed for apredetermined amount of time.

In some embodiments, replacing the display of the second text with theat least one affordance representing at least one calendar entry occursautomatically after the second text is displayed for the predeterminedamount of time.

In some embodiments, the at least one calendar entry is scheduled forthe current day.

In some embodiments, the first text indicating the at least two monthscomprises text indicating the names of the at least two months includingthe current month and a plurality of numerals indicating at least somedays of the current month, where the text and the plurality of numeralsassociated with the current month are displayed such that, as a unit,they span the vertical center of the display unit 3602.

In some embodiments, the second text indicating the at least some daysin the one and only month comprises a plurality of numerals indicatingat least some days of the current month, including the current day,where the display of the numeral indicating the current day spans thevertical center of the display unit 3602.

In some embodiments, the at least one affordance representing the atleast one calendar entry is a contiguous region visually distinguishablefrom a background of the calendar application.

In some embodiments, (a) and (b) are both performed.

The operations described above with reference to FIG. 25 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.36. For example, displaying operations 2502, 2508, 2512 and 2514;detecting operation 2504; determining operation 2506; and launchingoperation 2510 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 37 shows a functional blockdiagram of an electronic device 3700 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 37 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 37, an electronic device 3700 includes a display unit3702 configured to display a graphic user interface, a touch sensitivesurface unit 3704 configured to receive contacts, and a processing unit3706 coupled to the display unit 3702 and the touch-sensitive surfaceunit 3704. In some embodiments, the processing unit 3706 includes adisplay enabling unit 3708, a detecting unit 3710, and a replacing unit3712.

The processing unit 3706 is configured to enable display (e.g., with thedisplay enabling unit 3708) of, on the display unit 3702, an affordancerepresenting a calendar application; detect (e.g., with the detectingunit 3710) user input; in response to detecting the user input, (a) inaccordance with a determination that the detected user input is a touchon the displayed affordance: enable display (e.g., with the displayenabling unit 3708) of a first text indicating at least two months in ayear, then, replace (e.g., with the replacing unit 3712) the display ofthe first text with a display of a second text indicating at least somedays in one and only one month of the year, and then, replace (e.g.,with the replacing unit 3712) the display of the second text with adisplay of at least one affordance representing at least one calendarentry; and (b) in accordance with a determination that the detected userinput is a movement of a rotatable input mechanism, enable display(e.g., with the display enabling unit 3708) of the first text indicatingat least two months in a year.

In some embodiments, the movement of the rotatable input mechanism is afirst movement of the rotatable input mechanism, the processing unit3706 further configured to detect (e.g., with the detecting unit 3710) asecond movement of the rotatable input mechanism; and in response todetecting the second movement, replace (e.g., with the replacing unit3712) the display of the first text with a display of the second textindicating the at least some days in the one and only one month of theyear.

In some embodiments, the processing unit 3706 is further configured todetect (e.g., with the detecting unit 3710) a third movement of therotatable input mechanism; and in response to detecting the thirdmovement, replace (e.g., with the replacing unit 3712) the display ofthe second text with a display of the at least one user interface objectrepresenting the at least one calendar entry.

In some embodiments, replacing the display of the first text with thesecond text occurs automatically after the first text is displayed for apredetermined amount of time.

In some embodiments, replacing the display of the second text with theat least one user interface object representing at least one calendarentry occurs automatically after the second text is displayed for thepredetermined amount of time.

In some embodiments, the at least one calendar entry is scheduled forthe current day.

In some embodiments, the first text indicating the at least two monthscomprises text indicating the names of the at least two months includingthe current month, and a plurality of numerals indicating at least somedays of the current month, where the text and the plurality of numeralsassociated with the current month are displayed such that, as a unit,they span the vertical center of the display unit 3702.

In some embodiments, the second text indicating the at least some daysin the one and only month comprises a plurality of numerals indicatingat least some days of the current month, including the current day,where the display of the numeral indicating the current day spans thevertical center of the display unit 3702.

In some embodiments, the at least one affordance representing the atleast one calendar entry is a contiguous region visually distinguishablefrom a background of the calendar application.

In some embodiments, (a) and (b) are both performed.

The operations described above with reference to FIG. 26 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.37. For example, displaying operations 2602, 2608, 2612 and 2614;detecting operation 2604; determining operation 2606; and launchingoperation 2610 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 38 shows a functional blockdiagram of an electronic device 3800 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 38 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 38, an electronic device 3800 includes a display unit3802 configured to display a graphic user interface, a touch sensitivesurface unit 3804 configured to receive contacts, and a processing unit3806 coupled to the display unit 3802 and the touch-sensitive surfaceunit 3804. In some embodiments, the processing unit 3806 includes adisplay enabling unit 3808, a detecting unit 3810, a determining unit3812, and, optionally, a sending unit 3814, an initiating unit 3816, anda creating unit 3818.

The processing unit 3806 is configured to enable display (e.g., with thedisplay enabling unit 3808) of an affordance representing a calendarentry in a calendar application; detect (e.g., with the detecting unit3810) a touch on the display, the touch having a characteristicintensity, the touch located at the displayed user interface objectrepresenting the calendar entry; determine (e.g., with the determiningunit 3812) whether the characteristic intensity of the touch is below athreshold intensity; in response to a determination that thecharacteristic intensity of the touch is below the threshold intensity,enable display (e.g., with the display enabling unit 3808) of a time anda location associated with the calendar entry; and in response to adetermination that the characteristic intensity of the touch is notbelow the threshold intensity, enable display (e.g., with the displayenabling unit 3808) of, on the display unit 3802, a plurality ofaffordances representing functions of the calendar application.

In some embodiments, the processing unit 3806 is further configured to,in response to a determination that the characteristic intensity of thefirst touch is not below the threshold intensity, enable display (e.g.,with the display enabling unit 3808) of, on the display unit 3802, anaffordance for creating a calendar entry.

In some embodiments, enabling display of the plurality of affordancesrepresenting functions of the calendar application comprises enablingdisplay of an affordance that, when selected, sends an instruction toanother electronic device instructing the other electronic device todisplay a calendar entry.

In some embodiments, enabling display of the plurality of affordancesrepresenting functions of the calendar application comprises displayingan affordance that, when selected, displays a phone number associatedwith a calendar entry.

In some embodiments, the processing unit 3806 is further configured todetect (e.g., with the detecting unit 3810) user selection of theaffordance for enable display of the phone number; and in response todetecting the user selection, send (e.g., with the sending unit 3814) aninstruction to another electronic device instructing the otherelectronic device to initiate a phone call to the phone number.

In some embodiments, the processing unit 3806 is further configured todetect (e.g., with the detecting unit 3810) user selection of theaffordance for enable display of the phone number, and, in response todetecting the user selection, initiate (e.g., with the initiating unit3816) a phone call to the phone number.

In some embodiments, the phone number is associated with an organizer ofthe calendar entry.

In some embodiments, enabling display of the plurality of affordancesrepresenting functions of the calendar application comprises enablingdisplay of an affordance that, when selected, displays an e-mail addressassociated with a calendar entry.

In some embodiments, the processing unit 3806 is further configured todetect (e.g., with the detecting unit 3810) user selection of theaffordance for enable display of the e-mail address and in response todetecting the user selection, send (e.g., with the sending unit 3814) aninstruction to another electronic device instructing the otherelectronic device to create an e-mail draft, the e-mail draft listingthe displayed email address as a recipient.

In some embodiments, the processing unit 3806 is further configured todetect (e.g., with the detecting unit 3810) user selection of theaffordance for enable display of the e-mail address and, in response todetecting the user selection, create (e.g., with the creating unit 3818)an e-mail draft, the e-mail draft listing the displayed email address asa recipient.

In some embodiments, the e-mail address is associated with an organizerof the calendar entry.

In some embodiments, the other device is a cellular phone.

The operations described above with reference to FIG. 27 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.38. For example, displaying operations 2702, 2708, and 2710; detectingoperation 2704; and determining operation 2706 are, optionally,implemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 39 shows a functional blockdiagram of an electronic device 3800 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 39 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 39, an electronic device 3900 includes a display unit3902 configured to display a graphic user interface, a touch sensitivesurface unit 3904 configured to receive contacts, and a processing unit3906 coupled to the display unit 3902 and the touch-sensitive surfaceunit 3904. In some embodiments, the processing unit 3906 includes adisplay enabling unit 3908 and a receiving unit 3910.

The processing unit 3906 is configured to enable display (e.g., with thedisplay enabling unit 3908) of, on the display unit 3902, a plurality ofcalendar entries, the plurality of calendar entries including a firstcalendar entry and a second calendar entry, the first calendar entrydisplayed above the second calendar entry; receive (e.g., with thereceiving unit 3910) user input representing user acceptance of thefirst calendar entry; and in response to receiving the user input,enable display (e.g., with the display enabling unit 3908) of the firstcalendar entry below the second calendar entry.

In some embodiments, receiving user input representing user acceptanceof the first calendar entry comprises detecting a touch on thetouch-sensitive surface unit 3904 having a characteristic intensity, thetouch having a characteristic intensity; determining whether thecharacteristic intensity is above a threshold intensity; and in responseto a determination that the characteristic intensity is above thethreshold intensity, enabling display of an accept affordance foraccepting the calendar entry and an decline affordance for declining thecalendar entry; and detecting a user selection of the accept affordance.

In some embodiments, the processing unit 3906 is further configured to,in response to a determination that the characteristic intensity is notabove the threshold intensity, enable display (e.g., with the displayenabling unit 3908) of a time and location of the calendar entry.

In some embodiments, receiving user input representing user acceptanceof the first calendar entry comprises detecting a user selection of thefirst calendar entry; in response to detecting the user selection of thefirst calendar entry, enabling display of a time and location of thecalendar entry and enabling display of an accept affordance foraccepting the calendar entry; and detecting a user selection of theaccept affordance.

In some embodiments, the processing unit 3906 is further configured toin response to detecting the user selection of the accept affordance,enable display (e.g., with the display enabling unit 3908) of a visualindication indicating acceptance of the calendar entry.

In some embodiments, the visual indication comprises a messageconfirming acceptance of the calendar entry.

In some embodiments, enabling display of the plurality of calendarentries comprises enable display of calendar entries scheduled fordifferent days.

The operations described above with reference to FIG. 28 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.39. For example, displaying operations 2802 and 2806 and detectingoperation 2804 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 40 shows a functional blockdiagram of an electronic device 4000 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 40 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 40, an electronic device 4000 includes a display unit4002 configured to display a graphic user interface, a touch sensitivesurface unit 4004 configured to receive contacts, and a processing unit4006 coupled to the display unit 4002 and the touch-sensitive surfaceunit 4004. In some embodiments, the processing unit 4006 includes adisplay enabling unit 4008, a receiving unit 4010, a removal enablingunit 4012, and a replacing unit 4014.

The processing unit 4006 is configured to enable display (e.g., with thedisplay enabling unit 4008) of, on the display unit 4002, a first userinterface screen having a plurality of calendar entries; receive (e.g.,with the receiving unit 4010) first data representing user acceptance ofa first calendar entry of the plurality of calendar entries; in responseto receiving the first data, enable removal (e.g., with the removalenabling unit 4012) of the accepted first calendar entry from the firstuser interface screen; receive (e.g., with the receiving unit 4010)second data representing a user input; and in response to receiving thesecond data, replace (e.g., with the replacing unit 4014) the display ofthe first user interface screen with a display of a second userinterface screen having a plurality of accepted calendar entries.

In some embodiments, the user input is a movement of a rotatable inputmechanism of the electronic device.

In some embodiments, the user input is a swipe on the touch-sensitivesurface unit 4004 in a substantially horizontal direction.

In some embodiments, receiving first data representing user acceptanceof the first calendar entry comprises detecting a touch on thetouch-sensitive surface unit 4004, the touch having a characteristicintensity; determining whether the characteristic intensity is above athreshold intensity; in response to a determination that thecharacteristic intensity is above the threshold intensity, enablingdisplay of an accept affordance for accepting the calendar entry and andecline affordance for declining the calendar entry; and detecting auser selection of the accept affordance.

In some embodiments, the processing unit 4006 is further configured to,in response to a determination that the characteristic intensity is notabove the threshold intensity, enable display (e.g., with the displayenabling unit 4008) of a time and location of the calendar entry.

In some embodiments, receiving first data representing user acceptanceof the first calendar entry comprises detecting a user selection of thefirst calendar entry; in response to detecting the user selection,enabling display of a time and location of the calendar entry and anaccept affordance for accepting the calendar entry; and receiving a userselection of the accept affordance.

In some embodiments, the first and second user interface screens eachinclude an affordance indicating the currently displayed user interfacescreen and a position of the displayed user interface screen within asequence of the user interface screens.

The operations described above with reference to FIG. 29 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.40. For example, displaying operations 2902 and 2910, detectingoperations 2904 and 2908, and removing operation 2906 are, optionally,implemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 41 shows a functional blockdiagram of an electronic device 3500 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 41 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 41, an electronic device 4100 includes a display unit4102 configured to display a graphic user interface, a touch sensitivesurface unit 4104 configured to receive contacts, and a processing unit4106 coupled to the display unit 4102 and the touch-sensitive surfaceunit 4104. In some embodiments, the processing unit 4106 includes adisplay enabling unit 4108, a detecting unit 4110, a change enablingunit 4112 and, optionally, a return enabling unit 4114 and a designationunit 4116.

The processing unit 4106 is configured to enable display (e.g., with thedisplay enabling unit 4108) of a user interface screen on the displayunit 4102, where the displayed user interface screen includes aplurality of texts indicating a plurality of months in a year, the textsof the plurality of texts are organized according to a layout having atleast two rows and at least two columns, and the plurality of texts havean initial visual characteristic; detect (e.g., with the detecting unit4110) a user selection of a first text of the plurality of texts, thefirst text indicating a first month of the plurality of months; and inresponse to detecting the user selection, enable change (e.g., with thechange enabling unit 4112) of the visual characteristic of the pluralityof texts except the first text indicating the first month.

In some embodiments, the processing unit 4106 is further configured todetect (e.g., with the detecting unit 4110) a movement of the userselection of the first text, and in response to detecting the movement:enable change (e.g., with the change enabling unit 4112) of the visualcharacteristic of the first text indicating the first month and enablereturn (e.g., with the return enabling unit 4114) of the visualcharacteristic of a second text indicating a second month of theplurality of months to its initial visual characteristic.

In some embodiments, the first text and the second text representconsecutive months in the year.

In some embodiments, the user selection is a touch on thetouch-sensitive surface unit 4104 at a position of the displayed firsttext.

In some embodiments, the movement is a swipe of the touch.

In some embodiments, the movement is a substantially vertical movement.

In some embodiments, the processing unit 4106 is further configured todetect (e.g., with the detecting unit 4110) a release of the userselection of the first text and in response to detecting the release,enable designation (e.g., with the designation enabling unit 4116) thesecond text indicating the second month as having focus.

In some embodiments, the processing unit 4106 is further configured to,in response to detecting the release, enable return (e.g., with thereturn enabling unit 4114) of the visual characteristic of the pluralityof texts to the initial visual characteristic, except the second text.

In some embodiments, the change in visual characteristic comprises thevisual effect of dimming.

In some embodiments, the change in visual characteristic comprises thevisual effect of greying.

In some embodiments, the change in visual characteristic comprisesincreasing translucency.

In some embodiments, the change in visual characteristic comprises thevisual effect of darkening.

The operations described above with reference to FIG. 30 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.41. For example, displaying operation 3002; detecting operations 3004,3008, and 3012; changing operations 3006 and 3010, and designatingoperation 3014 are optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 42 shows a functional blockdiagram of an electronic device 4200 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 42 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 42, an electronic device 4200 includes a display unit4202 configured to display a graphic user interface, a touch sensitivesurface unit 4204 configured to receive contacts, and a processing unit4206 coupled to the display unit 4202 and the touch-sensitive surfaceunit 4204. In some embodiments, the processing unit 4206 includes adisplay enabling unit 4208, a translation enabling unit 4210 and,optionally, a labeling unit 4212 and a ceasing unit 4214.

The processing unit 4206 is configured to enable display (e.g., with thedisplay enabling unit 4208) of a row of numerals, the numeralsindicating days in a month; detect user input; and in response todetecting the user input, enable translation (e.g., with the translationenabling unit 4210) of all but one of the displayed numerals from itsrespective position in the row into a new position, where the displayednumerals, in their new positions, form a column of numerals.

In some embodiments, the numerals displayed in the new positionrepresent days in one week of the month.

In some embodiments, a numeral of the numerals is associated with a dayof a week, the processing unit 4206 further configured to, after thetranslating, label (e.g., with the labeling unit 4212) the numeral withtext identifying a day of the week.

In some embodiments, the processing unit 4206 is further configured toenable translation (e.g., with the translation enabling unit 4210) ofthe one remaining numeral from its position in the row of numerals to aposition in the column of numerals.

In some embodiments, the user input is a movement of a rotatable inputmechanism of the electronic device.

In some embodiments, enabling translation comprises enabling translationat least one displayed numeral visibly on the display unit 4202.

In some embodiments, the row of numerals is a first row of numerals, theprocessing unit 4306 further configured to enable display (e.g., withthe display enabling unit 4208) of a second row of numerals representingadditional days in the month; in response to detecting the user input,enable translation of (e.g., with the translation enabling unit 4210)the second row of numerals towards one or more edges of the display unit4202; and cease (e.g., with the ceasing unit 4214) to enable display ofthe second row of numerals.

The operations described above with reference to FIG. 31 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.42. For example, displaying operation 3102, detecting operation 3104,and translating operation 3106 are, optionally, implemented by eventsorter 170, event recognizer 180, and event handler 190. Event monitor171 in event sorter 170 detects a contact on touch-sensitive display112, and event dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 43 shows a functional blockdiagram of an electronic device 4300 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 43 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 43, an electronic device 4300 includes a display unit4302 configured to display a graphic user interface, a touch sensitivesurface unit 4304 configured to receive contacts, and a processing unit4306 coupled to the display unit 4302 and the touch-sensitive surfaceunit 4304. In some embodiments, the processing unit 4306 includes adisplay enabling unit 4308, a detecting unit 4310, an enlargementenabling unit 4312 and, optionally, a removal enabling unit 4314 and areduction enabling unit 4316.

The processing unit 4306 is configured to enable display (e.g., with thedisplay enabling unit 4308) of on the display unit 4302: text indicatinghours in a day, at least one region representing a calendar entryscheduled during the indicated hours, and text inside the at least oneregion indicating a name of the calendar entry; detect (e.g., with thedetecting unit 4310) user input representing a zoom-in or zoom-outcommand; in accordance with a determination that the user inputrepresents a zoom-in command: enable enlargement of (e.g., with theenlargement enabling unit 4312) the at least one region, and enabledisplay (e.g., with the display enabling unit 4308) of additional textinside the at least one region indicating details of the calendar entry.

In some embodiments, enabling display of additional text comprisesenabling display of one or more calendar entry information selected fromthe group consisting of calendar entry time, location, and organizer.

In some embodiments, the size of the enlarged at least one region isproportional to the duration of the calendar entry

In some embodiments, detecting user input comprises receiving datarepresenting movement of a rotatable input mechanism of the electronicdevice.

In some embodiments, detecting user input comprises receiving datarepresenting a de-pinching or pinching gesture on the touch-sensitivesurface unit 4304.

In some embodiments, the processing unit 4306 is further configured to,in accordance with a determination that the user input represents azoom-out command, enable removal (e.g., with the removal enabling unit4314) of the display of the text indicating days of the month and theuser interface object.

In some embodiments, the processing unit 4306 is further configured to,in accordance with a determination that the user input represents azoom-out command: enable reduction (e.g., with the reduction enablingunit 4316) of the size of the at least one region representing acalendar entry.

In some embodiments, the processing unit 4306 is further configured to,in accordance with a determination that the user input represents azoom-out command, enable display (e.g., with the display enabling unit4308) of a count of calendar entries within a time interval.

In some embodiments, the time interval is a month or a year.

The operations described above with reference to FIG. 32 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.43. For example, displaying operation 3202, detecting operation 3204 and1608, enlarging operation 3206, and removing operation 3208 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 44 shows a functional blockdiagram of an electronic device 4400 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 44 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 44, an electronic device 4400 includes a display unit4402 configured to display a graphic user interface, a touch sensitivesurface unit 4404 configured to receive contacts, and a processing unit4406 coupled to the display unit 4402 and the touch-sensitive surfaceunit 4404. In some embodiments, the processing unit 4406 includes adisplay enabling unit 4408, a detecting unit 4410, a launching unit 4412and, optionally, an enlargement enabling unit 4414.

The processing unit 4406 is configured to enable display (e.g., with thedisplay enabling unit 4408) of, on the display unit 4402, an applicationaffordance representing a calendar application; detect (e.g., with thedetecting unit 4410) a user selection of the application affordance; andin response to detecting the user selection of the applicationaffordance: launch (e.g., with the launching unit 4412) the calendarapplication, enable display (e.g., with the display enabling unit 4408)of a first event affordance representing a first calendar entry, andenable display (e.g., with the display enabling unit 4408) of a secondevent affordance representing a second calendar entry, where the secondcalendar entry is longer in duration than the first calendar entry, butthe size of the first event affordance is larger than the size of thesecond event affordance.

In some embodiments, the second calendar entry is an all-day calendarentry.

In some embodiments, the processing unit 4406 is further configured todetect (e.g., with the detecting unit 4410) user selection of the secondevent affordance and, in response to detecting the user selection of thesecond event affordance, enable enlargement (e.g., with the enlargementenabling unit 4414) of the second affordance.

In some embodiments, the enlarged second affordance includes textrepresenting the name of the second calendar entry.

In some embodiments, only one of the first affordance and the secondaffordance includes text representing a name of the first calendarentry.

In some embodiments, the second event affordance representing theall-day calendar entry is displayed on top of all other displayedaffordances representing calendar entries.

In some embodiments, detecting user selection of the second eventaffordance comprises detecting a touch on the touch-sensitive surfaceunit 4404 at a position of the displayed second event affordance.

In some embodiments, wherein detecting user selection of the secondevent affordance comprises detecting a touch on the touch-sensitivesurface unit 4404 at a position of the displayed second event affordanceand a movement of the touch.

In some embodiments, detecting user selection of the second eventaffordance comprises detecting a touch on the touch-sensitive surfaceunit 4404 at a position of the displayed second event affordance and amovement of the touch above a threshold distance.

The operations described above with reference to FIG. 33 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.44. For example, displaying operation 3302, detecting operations 3304and 3308, launching operation 3306, and enlarging operation 3310 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying figures, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe appended claims.

What is claimed is:
 1. An electronic device, comprising: atouch-sensitive display; one or more processors; a memory; and one ormore programs, wherein the one or more programs are stored in the memoryand configured to be executed by the one or more processors, the one ormore programs including instructions for: displaying on thetouch-sensitive display: text indicating hours in a day, at least oneregion representing a calendar entry scheduled during the indicatedhours, and text inside the at least one region indicating a name of thecalendar entry; detecting user input representing a zoom-in or zoom-outcommand; in accordance with a determination that the user inputrepresents a zoom-in command: enlarging the at least one region, anddisplaying additional text inside the at least one region indicatingdetails of the calendar entry.
 2. The electronic device of claim 1,wherein displaying additional text comprises displaying one or morecalendar entry information selected from the group consisting ofcalendar entry time, location, and organizer.
 3. The electronic deviceof claim 1, wherein a size of the enlarged at least one region isproportional to the duration of the calendar entry
 4. The electronicdevice of claim 1, wherein detecting user input comprises receiving datarepresenting movement of a rotatable input mechanism of the electronicdevice.
 5. The electronic device of claim 1, wherein detecting userinput comprises receiving data representing a de-pinching or pinchinggesture on the touch-sensitive display.
 6. The electronic device ofclaim 1, the one or more programs further including instructions for: inaccordance with a determination that the user input represents azoom-out command: removing the display of the text indicating days ofthe month.
 7. The electronic device of claim 1, the one or more programsfurther including instructions for: in accordance with a determinationthat the user input represents a zoom-out command: reducing a size ofthe at least one region representing a calendar entry.
 8. The electronicdevice of claim 1, the one or more programs further includinginstructions for: in accordance with a determination that the user inputrepresents a zoom-out command: displaying a count of calendar entrieswithin a time interval.
 9. The electronic device of claim 8, wherein thetime interval is a month or a year.
 10. A method, comprising: at anelectronic device with a touch-sensitive display: displaying on thetouch-sensitive display: text indicating hours in a day, at least oneregion representing a calendar entry scheduled during the indicatedhours, and text inside the at least one region indicating a name of thecalendar entry; detecting user input representing a zoom-in or zoom-outcommand; in accordance with a determination that the user inputrepresents a zoom-in command: enlarging the at least one region, anddisplaying additional text inside the at least one region indicatingdetails of the calendar entry.
 11. A non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of an electronic device with a touch-sensitivedisplay, the one or more programs including instructions for: displayingon the touch-sensitive display: text indicating hours in a day, at leastone region representing a calendar entry scheduled during the indicatedhours, and text inside the at least one region indicating a name of thecalendar entry; detecting user input representing a zoom-in or zoom-outcommand; in accordance with a determination that the user inputrepresents a zoom-in command: enlarging the at least one region, anddisplaying additional text inside the at least one region indicatingdetails of the calendar entry.